Repository navigation
Conversation
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>
September 29: published 7.2.5 topic ports; qualification hold remainsThe six prepared ports are now published on the same pinned refresh base
The original PR heads remain unchanged as review/history records. No duplicate Re-running the replay audit passed for all 54 commits: author identity/date, Updated v1 hardware status (supersedes the earlier pending-install status)The actual candidate was
Do not repeat the failed suspend test or stimulate speakers unattended. The PR #51 and #52 remain draft / DO NOT MERGE. Publication does not change beta's |
Current held 7.2.5 review stackThe already-published topic refs now have dedicated draft PRs. These expose the
Fresh API and Git checks verify the exact base/head/count of every draft and The latest Golden head has its own completed raw-source build/inspection, The current workflow runs automatically only for beta-targeted PRs, not these Do not merge into the staging dependency branches or final beta yet. Qualify the |
|
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 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. |
Jens rebased
jg/ubuntu-qcom-x1e-7.2.yonto Linux 7.2.5 ate57ec2987d45. 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
eea051659232has parentsbf631f9a13b3(existing beta) ande57ec2987d45(new upstream).86b7545b3586, absent from the rewritten upstream.bdae86ee3b4eupdates 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
W=1focused builds pass for touch/pen, GPI/GENI, display/HID, IMX681, complete CAMSS, C-PHY, DWC3, SPI core and battmgr.3fb28cf091ac3b75624390134f92bf5d2dd7014f96a293d4bd0487ee170338d1.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, ABI7.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.