From: Neil Armstrong <neil.armstrong@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [PATCH v3 0/9] arm64: dts: qcom: Set up 4-lane DP for sm8[56]50 & x1e boards
Date: Fri, 22 Aug 2025 17:56:48 +0200 [thread overview]
Message-ID: <20250822-topic-x1e80100-4lanes-v3-0-5363acad9e32@linaro.org> (raw)
Now the 4lanes support in the QMP Combo PHY has been merged in [1],
add the required plumbing in DT.
[1] https://lore.kernel.org/all/20250807-topic-4ln_dp_respin-v4-0-43272d6eca92@oss.qualcomm.com/
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
---
Changes in v3:
- Move the data-lanes in the SoC dtsi, and update it there
- Link to v2: https://lore.kernel.org/r/20250822-topic-x1e80100-4lanes-v2-0-4b21372b1901@linaro.org
Changes in v2:
- Add missing x1-asus-zenbook-a14 & x1-crd
- Link to v1: https://lore.kernel.org/r/20250821-topic-x1e80100-4lanes-v1-0-0b1a0d093cd5@linaro.org
---
Neil Armstrong (9):
arm64: dts: qcom: sm8550: allow mode-switch events to reach the QMP Combo PHY
arm64: dts: qcom: sm8650: allow mode-switch events to reach the QMP Combo PHY
arm64: dts: qcom: x1e80100: allow mode-switch events to reach the QMP Combo PHYs
arm64: dts: qcom: sm8550: move dp0 data-lanes to SoC dtsi
arm64: dts: qcom: sm8650: move dp0 data-lanes to SoC dtsi
arm64: dts: qcom: x1e80100: move dp0/1/2 data-lanes to SoC dtsi
arm64: dts: qcom: sm8550: Set up 4-lane DP
arm64: dts: qcom: sm8650: Set up 4-lane DP
arm64: dts: qcom: x1e80100: Set up 4-lane DP
arch/arm64/boot/dts/qcom/sm8550-hdk.dts | 4 ----
arch/arm64/boot/dts/qcom/sm8550-mtp.dts | 4 ----
arch/arm64/boot/dts/qcom/sm8550-qrd.dts | 4 ----
arch/arm64/boot/dts/qcom/sm8550.dtsi | 2 ++
arch/arm64/boot/dts/qcom/sm8650-hdk.dts | 4 ----
arch/arm64/boot/dts/qcom/sm8650-qrd.dts | 4 ----
arch/arm64/boot/dts/qcom/sm8650.dtsi | 2 ++
arch/arm64/boot/dts/qcom/x1-asus-zenbook-a14.dtsi | 2 --
arch/arm64/boot/dts/qcom/x1-crd.dtsi | 3 ---
arch/arm64/boot/dts/qcom/x1e001de-devkit.dts | 3 ---
arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi | 2 --
arch/arm64/boot/dts/qcom/x1e80100-dell-xps13-9345.dts | 2 --
arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts | 2 --
arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts | 3 ---
arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi | 2 --
arch/arm64/boot/dts/qcom/x1e80100-qcp.dts | 3 ---
arch/arm64/boot/dts/qcom/x1e80100.dtsi | 6 ++++++
17 files changed, 10 insertions(+), 42 deletions(-)
---
base-commit: 7fa4d8dc380fbd81a9d702a855c50690c9c6442c
change-id: 20250821-topic-x1e80100-4lanes-a8dd7f1cd569
Best regards,
--
Neil Armstrong <neil.armstrong@linaro.org>
next reply other threads:[~2025-08-22 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 15:56 Neil Armstrong [this message]
2025-08-22 15:56 ` [PATCH v3 1/9] arm64: dts: qcom: sm8550: allow mode-switch events to reach the QMP Combo PHY Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 2/9] arm64: dts: qcom: sm8650: " Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 3/9] arm64: dts: qcom: x1e80100: allow mode-switch events to reach the QMP Combo PHYs Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 4/9] arm64: dts: qcom: sm8550: move dp0 data-lanes to SoC dtsi Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 5/9] arm64: dts: qcom: sm8650: " Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 6/9] arm64: dts: qcom: x1e80100: move dp0/1/2 " Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 7/9] arm64: dts: qcom: sm8550: Set up 4-lane DP Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 8/9] arm64: dts: qcom: sm8650: " Neil Armstrong
2025-08-22 15:56 ` [PATCH v3 9/9] arm64: dts: qcom: x1e80100: " Neil Armstrong
2025-08-22 18:13 ` [PATCH v3 0/9] arm64: dts: qcom: Set up 4-lane DP for sm8[56]50 & x1e boards Dmitry Baryshkov
2025-09-01 19:46 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250822-topic-x1e80100-4lanes-v3-0-5363acad9e32@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).