Skip to content

[QUALIFICATION - DO NOT MERGE] Refresh SP11 beta onto rebased 7.2.5 - #51

Closed
ooaklee wants to merge 2082 commits into
sp11/ubuntu-qcom-x1e-7.2.y-betafrom
x/sync-jg-7.2.5-20260928
Closed

ooaklee wants to merge 2082 commits into
sp11/ubuntu-qcom-x1e-7.2.y-betafrom
x/sync-jg-7.2.5-20260928

Conversation

@ooaklee

@ooaklee ooaklee commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Jens rebased jg/ubuntu-qcom-x1e-7.2.y onto Linux 7.2.5 at e57ec2987d45. This draft refreshes the existing SP11 beta tree against that exact upstream while retaining the old beta and contributor history.

Qualification only: do not merge yet. No hardware pass is claimed, and none of the held runtime topics is folded into this refresh. Package verification for the separate refresh-plus-GPI test carrier is recorded in #52.

Composition and preservation

  • Refresh merge eea051659232 has parents bf631f9a13b3 (existing beta) and e57ec2987d45 (new upstream).
  • Its tree was reconstructed by replaying the 32 already-merged SP11 commits. All author identities, author dates, subjects and edits are preserved. Thirty-one stable patch IDs match; the remaining touchscreen DT patch has identical edits with different surrounding context.
  • Retain Abel Vesa's existing Denali EC-reset GPIO reservation from 86b7545b3586, absent from the rewritten upstream.
  • Retain upstream's new PS883x compatible-based USB4 restriction, SPI-core DMA cleanup, battmgr fixes and packaging. Removal of the old DT USB4 property does not imply USB4 support.
  • Final commit bdae86ee3b4e updates only CI. It pins the new upstream and exact refresh commit, checks both parents, and retains strict linear per-commit checks for normal topic PRs.

The 740 old-only / 2,080 new-only upstream commits make a naive history merge unsuitable. Reconstructing from the new upstream avoids reintroducing unrelated old board changes. The public beta and the existing v10/topic PRs remain unchanged.

Verification

  • Exact-source ARM64 GCC 13.3 W=1 focused builds pass for touch/pen, GPI/GENI, display/HID, IMX681, complete CAMSS, C-PHY, DWC3, SPI core and battmgr.
  • MSHW0485 also compiles with both optional pen interfaces disabled.
  • OLED, LCD and Dell XPS 13 9345 DTBs build. The Dell DTB is byte-identical to a separate pristine-upstream build: 3fb28cf091ac3b75624390134f92bf5d2dd7014f96a293d4bd0487ee170338d1.
  • Selected touch/sensor/SPI/DWC3 binding documents, examples and DTB checks pass. Global schema preparation reports an unrelated upstream ath12k YAML warning and a jobserver warning.
  • The updated integration validator passes. Six tests cover the approved refresh, ordinary linear topic, rejected arbitrary merge, rejected different merge with identical parents, rejected stale topic and rejected empty range.
  • A separate synthetic GitHub PR merge passes the actual pull-request event path without review-range environment overrides.
  • All 33 replay commits were inspected. The unchanged USB quirk retains three historical alignment checks; aggregate checkpatch reports zero errors, three warnings and three checks. No warning waiver was added.
  • Upstream-relative whitespace checks pass. The full old-beta-to-refresh diff retains one upstream changelog trailing space.

These checks establish source preservation and bounded software compatibility, not hardware behavior. The separate v24 child in #52 has now passed full package and local artifact verification; that is not an installation or physical qualification of this refresh. The new upstream SPI fix does not prove the touchscreen freeze is resolved.

OpenCode/Zai-Codex GLM-5.1 reviewed the final validator and recorded source/build evidence. It found no demonstrated bypass in the exact-commit exception and gave conditional source-review approval. Its conditions were checked: the pinned upstream still matches the remote, and the workflow invokes the validator without review-range overrides. This does not supply a hardware approval.

Current qualification sequence — October 4

The isolated #52/v1 carrier and old cumulative trials are closed as superseded
review vehicles; their failures remain evidence. The current exact combined
candidate is #68, 8ba2b75713feb5c72bbc11dd8cce4048e23cdeea, ABI
7.2.5-jg-0sp11v8-qcom-x1e. It has finished-package, installed-boot-binding,
human ordinary-use and bounded Power Saver camera/quiet-playback evidence in
the qualification report. That is not a standalone hardware
acceptance of this refresh head or a waiver of its remaining composition gates.

Retain focused #56 camera, #57 TX, #58 playback, #59 battery, #60 profiles and
#61 GPI; CI-only #62/#64/#66 stay separate. Complete targeted source/lifecycle
dispositions, contributor clarification, documented deviations and fork-only
complete CI rollout before accepting one final composition into beta. Recheck
upstream immediately before promotion. Do not merge every cumulative trial.
The two additional GPI corrections remain deferred in
OE #67, preserving tested v8 source.

V23 remains the recovery/default reference. No source, branch refs or draft
state changes accompany this documentation update; fork CI must not be shipped
in the later focused upstream submissions.

jglathe and others added 30 commits September 16, 2026 22:34
amend the following files for the new mdss_dp3_out definition:

arch/arm64/boot/dts/qcom/x1-acer-swift-14.dtsi
arch/arm64/boot/dts/qcom/x1-asus-vivobook-s15.dtsi
arch/arm64/boot/dts/qcom/x1-hp-omnibook-x14.dtsi
arch/arm64/boot/dts/qcom/x1p42100-lenovo-ideapad-5-2in1.dts
arch/arm64/boot/dts/qcom/x1p42100-lenovo-ideapad-slim5x.dts

refers-to: 24f44be

also add the edp0_hpd_default pinctrl on dp3.

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
slim5x: i2c0: correct pinctrl-0
5-2in1: add commented- out dedicated driver atna40ct01

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
… 3 15Q8X10

add x126100 chip designation and compatible
add initial device tree

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
…ncept ISO

needs to boot and have efivars - use Thinkpad T14s as compatible
also added Vivobook 15 x1p42100
also added HP Omnibook X 14-fe1
also added Thinkbook 16
also added Acer Swift Go 14
also added Surface Pro 12"

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
fix typos in tlmm definition

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
since calculating tlmmgpio was unsuccessfful, use the common known one: tlmm 3

remove all possible touchpads except for the actual detected one, @38
disable all sophisticated pinctrl, only on the i2c devices

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
shared with keyboard, f yeah

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
since its apparently shared with the keyboard, disable it for now
there needs to be a mux driver which does the handling for it

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
required for 6.17

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
add dependency for python3-libfdt
add stubble-script hwids/finddtbs.py as debian/scripts/misc/find-dtbs.py

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
… T14s

T14s is powerful, but the fan doesn't cool it enough for full load.
Tone it down to the experimentally determined limits
QMP Combo PHYs default to USB3DP lane routing, which can break static setups like
DP-to-HDMI bridges by misallocating lanes to USB3.
Revive the optional "qcom,combo-initial-mode" DT property [1] to explicitly
set the initial mode ("usb3dp", "dp", "usb3"). In static configs (no mode-switch
or orientation-switch props), honor it and skip lane inference to avoid overrides.
This simplifies HDMI enablement on undocumented Snapdragon X laptops while
preserving dynamic Type-C behavior.

[1]: https://lore.kernel.org/r/20250821-topic-x1e80100-hdmi-v1-2-f14ad9430e88@linaro.org

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Microsoft Surface Pro 12 is using this (well, my definition of it), changed to
Stephan Gerhold's one.

Remove the edp0_hpd_default reference from Thinkbook 16 as TLMM 119 is used by the HDMI bridge
as enable pin.

Link: https://lore.kernel.org/r/20250822-x1e80100-add-edp-hpd-v2-1-6310176239a6@linaro.org

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
…to dp controller, fix backlight"

now duplicate template, therefore remove it

Link: https://lore.kernel.org/r/20250822-x1e80100-add-edp-hpd-v2-1-6310176239a6@linaro.org

This reverts commit 22f5ffacc9cd4f5a5074b863223f80bc0f0d6b33.
…lt pinctrl

seems to be needed

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Relates-to commit 8c0b058.

Signed-off-by: James Addison <jay@jp-hosting.net>
adding the remaining commits of 20251101-asus_usbc_dp-v1-0-9fd4eb9935e8@hotmail.com
... but on the generalized x1-asus-vivobook-s15.dtsi

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
this works with Ubuntu kernel builds that don't know the SPRCHRGD in QSEECOM

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
found in Lenovo Ideapad Slim 3 15Q8X10

raw EDID:

00 ff ff ff ff ff ff 00 09 e5 ea 0c 00 00 00 00
0c 22 01 04 a5 21 15 78 03 af e5 97 5e 58 92 28
1f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 9c 3e 80 c8 70 b0 3c 40 30 20
36 00 49 ce 10 00 00 1a 00 00 00 fd 00 28 3c 4c
4c 10 01 0a 20 20 20 20 20 20 00 00 00 fe 00 42
4f 45 20 43 51 0a 20 20 20 20 20 20 00 00 00 fc
00 4e 56 31 35 33 57 55 4d 2d 4e 34 31 0a 01 63

70 20 79 02 00 81 00 15 74 1a 00 00 03 01 28 3c
00 00 53 4a 53 4a 3c 00 00 00 00 80 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 90

Detailed Timing Descriptors:
DTD 1:
1920x1200   60.002995 Hz  16:10    75.604 kHz    160.280000 MHz (329 mm x 206 mm)
   Hfront   48 Hsync  32 Hback  120 Hpol P
   Vfront    3 Vsync   6 Vback   51 Vpol N

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
like on Thinkbook 16 and Ideapad 5

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
seem to be problematic

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
as tested out by Anthony Ruhier and Val Packett [1]

[1]: https://lore.kernel.org/all/a5efb372-1a2a-4262-abc8-49bbeffa6961@packett.cool/

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
name change from x1e80100 and x1p42100

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
@ooaklee

ooaklee commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner Author

September 29: published 7.2.5 topic ports; qualification hold remains

The six prepared ports are now published on the same pinned refresh base
bdae86ee3b4ef317df96b0e2e1b3a77c15b9a221, containing current upstream
e57ec2987d4540fa89280d349f79c4d9bcd7cf27. This is review publication, not a
merge or hardware-acceptance claim. Public beta remains at bf631f9a13b3.

Existing review Published 7.2.5 branch Head Immediate dependency
#40 camera x/sp11-camera-7.2.5-20260928 7e4c2c58713e refresh
#36 TX DMIC x/sp11-tx-7.2.5-20260928 7a8e9b112672 refresh
#47 Golden x/sp11-golden-7.2.5-20260928 3cfbd3b5e025 TX above
#37 battery x/sp11-battery-7.2.5-20260928 53905a94e735 refresh
#38 profile x/sp11-profile-7.2.5-20260928 af4d11ea9471 battery above
#45 GPI x/sp11-gpi-7.2.5-20260928 f9c68b9c62f6 refresh

The original PR heads remain unchanged as review/history records. No duplicate
topic PRs, force-pushes, branch deletions or final integration were performed.

Re-running the replay audit passed for all 54 commits: author identity/date,
subject, message except the source trailer, touched paths and context-independent
patch identity are preserved. The completed camera, TX, TX/Golden, battery and
battery/profile full-source builds and artifact checks remain software evidence
only. Their outputs are not installable Debian bundles or hardware qualification.
The Golden author-attestation gate remains unresolved; no certification or
authorship was invented or changed.

Updated v1 hardware status (supersedes the earlier pending-install status)

The actual candidate was 7.2.5-jg-0sp11v1-qcom-x1e, built from #52 at
e89ea031c208450ca56f342346d74bff0eb809b1. It already contains current upstream,
plus the GPI fix and packaging entry, but not the held TX/Golden or other topic
ports above. The historical carrier branch name still contains v24.

  • Installation succeeded using the fix now merged as fix: scope kernel boot validation to its owning installation lexr.sh#72.
  • The user reported sustained touch and pen checks passed.
  • Suspend hard-failed and required a forced power cycle. The last PM milestone
    was PM: suspend entry (deep), followed by filesystem sync completion and no
    recorded resume; failed entry versus failed resume is unresolved.
  • A blocked driver-probe worker was observed before suspend and again on the
    next boot. Its relationship to suspend is not proven.
  • ALSA exposed no sound cards. This incomplete input-only stack cannot qualify
    the untested TX/Golden port, and missing patches alone do not prove causation.
  • The user returned to v23 and confirmed touch, pen and audio work. V23 remains
    the verified default and recovery kernel.

Do not repeat the failed suspend test or stimulate speakers unattended. The
next comparison should retain the same upstream/config/toolchain and GPI input
repair while varying the audio dependency group. Passive boot-time diagnostics
are still runtime evidence and cannot by themselves establish the suspend cause.

PR #51 and #52 remain draft / DO NOT MERGE. Publication does not change beta's
role or waive hardware, non-SP11 containment, provenance or final-integration gates.

@ooaklee

ooaklee commented Sep 30, 2026

Copy link
Copy Markdown
Owner Author

Current held 7.2.5 review stack

The already-published topic refs now have dedicated draft PRs. These expose the
maintainer-topic/dependency split for review without moving beta, replacing the
older 7.2.2 PR heads or combining all topics into a test kernel.

Topic Current draft Immediate review dependency Head / topic commits
Camera #56 Refresh #51 7e4c2c58713e / 7
TX DMIC #57 Refresh #51 7a8e9b112672 / 3
Golden protected playback #58 TX #57 0428f5911523 / 46
Battery/AC providers #59 Refresh #51 53905a94e735 / 2
Platform profile/fan/CPU policy #60 Battery #59 af4d11ea9471 / 3
GPI event ordering #61 Refresh #51 f9c68b9c62f6 / 1

Fresh API and Git checks verify the exact base/head/count of every draft and
unchanged beta plus historical #40/#36/#47/#37/#38/#45 heads. All six explicit
immediate-base local integration/per-commit review ranges pass. Authors and
cherry-pick provenance remain retained, including documented registry context
adaptations; Golden contributor/DCO attestation remains unresolved.

The latest Golden head has its own completed raw-source build/inspection,
documented in #58 and the
exact-head checkpoint.
The v4 carrier and finished package bundle in #55 remain a separate diagnostic
track: GPI and ABI allocation are outside the dedicated Golden topic. V3's
physical static/squelching failure remains authoritative negative evidence.

The current workflow runs automatically only for beta-targeted PRs, not these
stacked drafts
. Their bodies disclose this and leave final beta-relative
composition/integration CI open. No automatic-CI success or hardware pass is
claimed from these local checks. No workflow has been weakened.

Do not merge into the staging dependency branches or final beta yet. Qualify the
base and each dependency group, document/accept deviations, then prepare and
revalidate the exact final beta-relative composition. All hardware, loaded-DSP,
protection, non-Denali, input/camera/power, suspend/resume and contributor gates
remain open. Keep working v23 as the recovery reference/default/fallback.

@ooaklee

ooaklee commented Oct 20, 2026

Copy link
Copy Markdown
Owner Author

Closed as an inactive/consolidated review vehicle during the 20 October kernel queue cleanup—not merged, newly hardware-qualified or accepted for upstream by this closure.

Previously recorded v8 acceptance evidence stands unchanged; this closure only retires the review vehicle.

The original source head and contributor history remain retained. Where a closed topic branch is removed, its verified archive/pr-51-20261020 tag preserves the exact head for recovery. Released/recovery/dependency branches remain untouched.

The separate tested-source staging route and all outstanding upstream reconstruction, provenance, fork-CI and deviation/promotion gates are tracked in OE #33. Experimental reverse-engineering PRs remain separate and unmerged. Beta/default branches and installed kernels are unchanged.

Retained exact source: bdae86ee3b4ef317df96b0e2e1b3a77c15b9a221.
Dated consolidation record: ooaklee/linux-surface-pro-11-oe#33 (comment)

@ooaklee ooaklee closed this Oct 20, 2026
@ooaklee
ooaklee deleted the x/sync-jg-7.2.5-20260928 branch October 20, 2026 19:58
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.