From: Tapas Rana <tapas.rana@oss.qualcomm.com>
To: andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
abel.vesa@oss.qualcomm.com, dmitry.baryshkov@oss.qualcomm.com,
konrad.dybcio@oss.qualcomm.com, 26rote@gmail.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tapas Rana <tapas.rana@oss.qualcomm.com>
Subject: [PATCH] arm64: dts: qcom: glymur: Add mode-switch to the USB controllers
Date: Tue, 17 Nov 2026 17:08:34 +0530 [thread overview]
Message-ID: <20261117113834.925310-1-tapas.rana@oss.qualcomm.com> (raw)
When the USB3-DP combo PHY is a mode switch, DisplayPort pin
assignments C and E put it in DP-only mode, where it stops the USB3
PIPE clock. Add mode-switch to the USB controllers as well, so that
they get the Type-C mode, move to the UTMI clock first and keep their
USB 2.0 ports working.
Signed-off-by: Tapas Rana <tapas.rana@oss.qualcomm.com>
---
Depends on Joonhoe Kim's dwc3 mode-switch series, which adds the
mode-switch binding and registers the controller as a Type-C mux in
dwc3-qcom. Without it, pmic_glink_altmode defers its probe
indefinitely:
https://lore.kernel.org/all/20261112113838.506-1-26rote@gmail.com/
arch/arm64/boot/dts/qcom/glymur.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
index 65a398c0a992..e9469bb7a832 100644
--- a/arch/arm64/boot/dts/qcom/glymur.dtsi
+++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
@@ -4998,6 +4998,7 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
snps,dis_u2_susphy_quirk;
snps,dis_enblslpm_quirk;
+ mode-switch;
usb-role-switch;
wakeup-source;
@@ -5088,6 +5089,7 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
snps,dis_u2_susphy_quirk;
snps,dis_enblslpm_quirk;
+ mode-switch;
usb-role-switch;
wakeup-source;
@@ -5178,6 +5180,7 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
snps,dis_u2_susphy_quirk;
snps,dis_enblslpm_quirk;
+ mode-switch;
usb-role-switch;
wakeup-source;
--
2.43.0
reply other threads:[~2026-11-17 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261117113834.925310-1-tapas.rana@oss.qualcomm.com \
--to=tapas.rana@oss.qualcomm.com \
--cc=26rote@gmail.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®