Skip to content

arm64: dts: qcom: x1-denali: add volume keys - #82

Merged
jglathe merged 2 commits into
jglathe:jg/ubuntu-qcom-x1e-7.2.yfrom
ooaklee:x/sp11-denali-dt
Sep 1, 2026
Merged

arm64: dts: qcom: x1-denali: add volume keys#82
jglathe merged 2 commits into
jglathe:jg/ubuntu-qcom-x1e-7.2.yfrom
ooaklee:x/sp11-denali-dt

Conversation

@ooaklee

@ooaklee ooaklee commented Aug 31, 2026

Copy link
Copy Markdown

Summary

  • describe the Surface Pro 11 volume-up key on PM8550 GPIO 6
  • describe the Surface Pro 11 volume-down key on PM8550 GPIO 8
  • enable autorepeat for the hardware volume rocker
  • keep the shared pon_resin node disabled

Scope and dependency

This is the first release-line topic extracted from the working -sp11 staging branch after #81. It is based directly on jg/ubuntu-qcom-x1e-7.2.y at 032e174490d2 and has no topic-PR dependency.

The change is limited to x1-microsoft-denali.dtsi. It does not carry the canceled CL4/PSCI experiment, USB changes, touch, pen, camera, audio, battery, or shared-driver changes from the staging history. The existing Denali firmware paths, rfkill setting, reserved GPIOs, and display backlight support are already present in the target branch and are therefore not replayed here.

The volume-down staging replay had retained an obsolete pon_resin override. #81 removed that replay omission from the staging branch; this release-line topic starts from the final intended state and never adds the override.

Provenance

The two focused commits retain links to the original SP11 integration work:

The older ooaklee alias on the volume-down commits has been normalized to the contributor's signed identity, Leon Silcott <leon@boasi.io>.

Validation

  • git diff --check 032e174490d2..HEAD
  • scripts/checkpatch.pl --strict --git 032e174490d2..HEAD: no errors or warnings
  • clean ARM64 ubuntu_x1e_defconfig DT build with CHECK_DTBS=y and dtschema 2025.8
  • qcom/x1e80100-microsoft-denali-oled.dtb builds successfully
  • qcom/x1p64100-microsoft-denali.dtb builds successfully
  • both compiled DTBs contain the volume-up and volume-down keys with the expected GPIOs/keycodes, and neither contains a pon_resin enablement
  • the same final volume-key state was included in the SP11: fix volume-down replay and preserve 7.2.2 GPI/SPI behavior #81 test kernel; it booted on Surface Pro 11 hardware and the changes were confirmed working

Cross-device impact

There are no shared-driver or non-Denali DT changes in this PR. Both supported Surface Pro 11 DTBs include the common Denali file and were validated above; other X1E/X1P devices do not include it.

Describe the Surface Pro 11 volume-up key on PM8550 GPIO 6 as an
active-low wake-capable input with the required pull-up.

This carries the hardware-verified volume-up portion of the original
SP11 integration change without its obsolete pon_resin assumption.

Link: 070c486
Signed-off-by: Leon Silcott <leon@boasi.io>
Describe the Surface Pro 11 volume-down key on PM8550 GPIO 8 as an
active-low wake-capable input with the required pull-up. Enable
gpio-keys autorepeat for the hardware rocker.

The SP11 rocker is not wired through pon_resin, which remains disabled
by the shared base description. Keep properties before child nodes so
the gpio-keys node passes DT validation.

Link: 247858b
Link: e3b4bf3
Signed-off-by: Leon Silcott <leon@boasi.io>
@jglathe

jglathe commented Sep 1, 2026

Copy link
Copy Markdown
Owner

1 down, 41 to go. Thanks!

@jglathe

jglathe commented Sep 1, 2026

Copy link
Copy Markdown
Owner

This is a change that you can actually upstream (would recommend). It is isolated enough to practice the process.

@ooaklee

ooaklee commented Sep 1, 2026

Copy link
Copy Markdown
Author

This is a change that you can actually upstream (would recommend). It is isolated enough to practice the process.

I'm going to watch a YouTube video on this, then attempt it. Is there any other material you recommend I look at before starting the process?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants