Repository navigation
Conversation
remove the delete-node statement, no longer needed refers-to: d68d93c Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
fix typo Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Follow the example of other DP controllers and also eDP controller on SC7280 and move mdss_dp3_out endpoint declaration to the SoC DTSI. This slightly reduces the boilerplate in the platform DT files and also reduces the difference between DP and eDP controllers. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
… lanes on type-c Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
At the moment, we indirectly rely on the boot firmware to set up the pinctrl for the eDP HPD line coming from the internal display. If the boot firmware does not configure the display (e.g. because a different display is selected for output in the UEFI settings), then the display fails to come up and there are several errors in the kernel log: [drm:dpu_encoder_phys_vid_wait_for_commit_done:544] [dpu error]vblank timeout: 80020041 [drm:dpu_kms_wait_for_commit_done:524] [dpu error]wait for commit done returned -110 [drm:dpu_encoder_frame_done_timeout:2715] [dpu error]enc40 frame done timeout ... Fix this by adding the missing pinctrl for gpio119 (func1/edp0_hot and bias-disable according to the ACPI DSDT), which is defined as &edp0_hpd_default template in x1e80100.dtsi. Fixes: 6516961 ("arm64: dts: qcom: Add support for X1-based Asus Zenbook A14") Tested-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com> # FHD OLED Reviewed-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com> Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
…for eDP HPD At the moment, we indirectly rely on the boot firmware to set up the pinctrl for the eDP HPD line coming from the internal display. If the boot firmware does not configure the display (e.g. because a different display is selected for output in the UEFI settings), then the display fails to come up and there are several errors in the kernel log: [drm:dpu_encoder_phys_vid_wait_for_commit_done:544] [dpu error]vblank timeout: 80020041 [drm:dpu_kms_wait_for_commit_done:524] [dpu error]wait for commit done returned -110 [drm:dpu_encoder_frame_done_timeout:2715] [dpu error]enc40 frame done timeout ... Fix this by adding the missing pinctrl for gpio119 (func1/edp0_hot and bias-disable according to the ACPI DSDT), which is defined as &edp0_hpd_default template in x1e80100.dtsi. Fixes: 7d1cbe2 ("arm64: dts: qcom: Add X1E78100 ThinkPad T14s Gen 6") Tested-by: Christopher Obbard <christopher.obbard@linaro.org> Reviewed-by: Christopher Obbard <christopher.obbard@linaro.org> Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org> Tested-by: Neil Armstrong <neil.armstrong@linaro.org> # on Lenovo Thinkpad T14s OLED Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
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>
Enable the protocol-9 QSPI engine and GPI DMA channels only on Microsoft Denali, then describe the MSHW0485 touchscreen and its control GPIOs. Link: b1075e6 Signed-off-by: Leon Silcott <leon@boasi.io>
Accept the Surface Pro 11 X1P touchscreen product ID alongside the existing X1E product ID when validating the MSHW0485 device descriptor. Link: 3fc7c52 Signed-off-by: Justin White <kyjus25@gmail.com> Signed-off-by: Leon Silcott <leon@boasi.io>
Record the two opt-in MSHW0485 feature gates in the qcom-x1e annotations. Kconfig still defaults both options to n; this Ubuntu flavour explicitly enables them for Denali, whose device tree must also opt in before either endpoint registers. Link: 4c2356a Depends-on: jglathe#83 Signed-off-by: Leon Silcott <leon@boasi.io>
Integrate jglathe#83 for combined SP11 testing.
The event ring is allocated and published before either QSPI channel reaches ACTIVE_STATE. Using the active-channel predicate for the upper doorbell write therefore publishes only the low half of a 64-bit DMA address and can corrupt the completion stream. Detect a configured Denali QSPI channel for event-ring publication, and cache the root compatible so the SP11 completion workarounds remain gated away from common GPI users. Signed-off-by: Leon Silcott <leon@boasi.io>
|
Follow-up validation for the SP11 7.2.2 retrospective:
This is build/package validation. Touch and pen still require a physical boot/resume test on the Surface Pro 11. |
4943ee7 to
6407d62
Compare
68e1550 to
e57ec29
Compare
|
Withdrawing this older 7.2.2-era submission version without merging while we continue qualification of the repaired 7.2.5 source on the fork. Current source/dependency review is tracked in ooaklee/linux_ms_dev_kit-sp11#51, ooaklee/linux_ms_dev_kit-sp11#61 and the combined candidate ooaklee/linux_ms_dev_kit-sp11#68. These are review vehicles, not an upstream-ready replacement or proof of equivalence to this old PR head. The current combined source is This PR's branch and exact head The two additional deferred GPI corrections are explicitly deferred, not removed from an accepted fix list. V8's existing working GPI/touch implementation remains intact; the known residual risks and separate width-cast disposition are not waived. The inherited QSPI/GENI/touch and opt-in pen-ABI prerequisites are carried by ooaklee/linux_ms_dev_kit-sp11#51. ooaklee/linux_ms_dev_kit-sp11#61 covers an additional GPI ordering port only; it does not replace the complete touch/pen series. Fresh focused upstream submissions will preserve the contributing authors, source links and dependencies after exact combined acceptance and the appropriate shared-driver checks. Fork-only integration scripts/workflows and repository policy will be excluded. PR #79 remains open as the maintainer's coordination/provenance thread. |
Summary
Dependency and status
Review/merge after #82, the Denali DT baseline topic. This branch is nevertheless based directly on
jg/ubuntu-qcom-x1e-7.2.yat032e174490d2, so the shared-driver diff remains independently reviewable.This is the release-line QSPI/touch extraction planned after the working staging correction in merged #81. It does not replay #81 or the staging branch's complete driver files. The PR remains a draft until this exact re-lift has been installed and tested on Surface Pro 11 hardware.
The default-off pen/HIDRAW/heat-frame work will follow as a separate, explicitly gated topic and is not present here.
Containment
QCOM_GPI_QSPI; the existing SPI, I2C, and UART protocols are unchangedqcom,geni-qspicontroller property and themicrosoft,denaliroot compatiblemicrosoft,mshw0485and rejects non-Denali machines/dev/g6ts-heatThe current release base already contains
DMA_PRIVATEand the GENI SPI tracepoints. This series preserves them and creates no intentional diff for either facility.Provenance
The series keeps original authors where the source has a valid author sign-off:
x1e-nixos <noreply@scug.io>remains author of the QSPI DMA binding and current-tree GPI re-lift, derived from 19bed4c3b6c1Leon signs each rewritten/submitted commit as
Leon Silcott <leon@boasi.io>.Validation
git diff --check 032e174490d2..HEADpython3-ply: no errors or checks; only the generic new-file/MAINTAINERS prompt for the new binding and driver, both already covered by the existingINPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERSentryFILE_PATH_CHANGESwarning suppressed: no errors, warnings, or checksubuntu_x1e_defconfigW=1builds ofdrivers/dma/qcom/gpi.o,drivers/spi/spi-geni-qcom.o, anddrivers/input/touchscreen/mshw0485_touch.oqcom/x1e80100-microsoft-denali-oled.dtbbuilds and passes the selected checksqcom/x1p64100-microsoft-denali.dtbbuilds and passes the selected checksqcom/x1e80100-dell-xps13-9345.dtbbuilds successfullyDMA_PRIVATEand all existing GENI tracepoints remain intactHardware checks still required