From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: 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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Wesley Cheng <wesley.cheng@oss.qualcomm.com>
Subject: Re: [PATCH RFT 2/3] arm64: dts: qcom: glymur: Add USB related nodes
Date: Mon, 26 Jan 2026 15:44:45 +0100 [thread overview]
Message-ID: <cb08a156-d905-419f-88f1-77bd136c823f@oss.qualcomm.com> (raw)
In-Reply-To: <wh4qsgwl6drye2d227mv22pxz57cikp6ogabklo6fvlzljqafp@sgps7d52yp2d>
On 1/26/26 3:31 PM, Abel Vesa wrote:
> On 26-01-13 14:13:32, Konrad Dybcio wrote:
>> On 1/13/26 1:33 PM, Abel Vesa wrote:
>>> From: Wesley Cheng <wesley.cheng@oss.qualcomm.com>
>>>
>>> The Glymur USB system contains 3 USB type C ports, 1 USB multiport
>>> controller and a USB 2.0 only controller. This encompasses 5 SS USB QMP
>>> PHYs (3 combo and 2 uni) and 6 M31 eUSB2 PHYs. All controllers are SNPS
>>> DWC3 based, so describe them as flattened DWC3 QCOM nodes.
>>>
>>> Signed-off-by: Wesley Cheng <wesley.cheng@oss.qualcomm.com>
>>> Co-developed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> ---
>>
>> [...]
>>
>>>
>>> + usb_mp_hsphy0: phy@fa1000 {
>>> + compatible = "qcom,glymur-m31-eusb2-phy",
>>> + "qcom,sm8750-m31-eusb2-phy";
>>> +
>>> + reg = <0 0x00fa1000 0 0x29c>;
>>> + #phy-cells = <0>;
>>> +
>>> + clocks = <&tcsr TCSR_USB2_1_CLKREF_EN>;
>>> + clock-names = "ref";
>>> +
>>> + resets = <&gcc GCC_QUSB2PHY_HS0_MP_BCR>;
>>> +
>>> + status = "disabled";
>>> + };
>>> +
>>> + usb_mp_hsphy1: phy@fa2000 {
>>> + compatible = "qcom,glymur-m31-eusb2-phy",
>>> + "qcom,sm8750-m31-eusb2-phy";
>>> +
>>> + reg = <0 0x00fa2000 0 0x29c>;
>>> + #phy-cells = <0>;
>>> +
>>> + clocks = <&tcsr TCSR_USB2_2_CLKREF_EN>;
>>> + clock-names = "ref";
>>> +
>>> + resets = <&gcc GCC_QUSB2PHY_HS1_MP_BCR>;
>>> +
>>> + status = "disabled";
>>> + };
>>
>>
>> [...]
>>
>>> + usb1_ss0_hsphy: phy@fd3000 {
>>
>> Let's not repeat the mess introduced in hamoa..
>>
>> Perhaps let's fall back to usb_0 etc.?
>
> Sure. So then:
>
> USB SS[0-2] -> usb_[0-2]
> USB MP -> usb_mp
> USB 2.0 (USB20S in docs) -> ?
usb_hs
Konrad
next prev parent reply other threads:[~2026-01-26 14:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 12:33 [PATCH RFT 0/3] arm64: dts: qcom: glymur: Add USB support Abel Vesa
2026-01-13 12:33 ` [PATCH RFT 1/3] dt-bindings: usb: qcom,dwc3: Allow high-speed interrupt on Glymur, Hamoa and Milos Abel Vesa
2026-01-13 13:05 ` Konrad Dybcio
2026-01-15 18:51 ` Rob Herring (Arm)
2026-01-13 12:33 ` [PATCH RFT 2/3] arm64: dts: qcom: glymur: Add USB related nodes Abel Vesa
2026-01-13 13:13 ` Konrad Dybcio
2026-01-26 14:31 ` Abel Vesa
2026-01-26 14:44 ` Konrad Dybcio [this message]
2026-01-26 15:03 ` Abel Vesa
2026-01-27 11:41 ` Abel Vesa
2026-01-27 11:46 ` Konrad Dybcio
2026-01-27 22:26 ` Wesley Cheng
2026-01-28 9:38 ` Abel Vesa
2026-01-30 18:17 ` Wesley Cheng
2026-01-28 9:53 ` Konrad Dybcio
2026-01-31 0:11 ` Wesley Cheng
2026-02-02 12:35 ` Konrad Dybcio
2026-01-13 17:58 ` Dmitry Baryshkov
2026-01-13 12:33 ` [PATCH RFT 3/3] arm64: dts: qcom: glymur-crd: Enable USB support Abel Vesa
2026-01-13 18:02 ` Dmitry Baryshkov
2026-01-26 14:24 ` Abel Vesa
2026-01-26 17:52 ` Dmitry Baryshkov
2026-02-10 10:03 ` Abel Vesa
2026-01-20 12:07 ` Pankaj Patil
2026-01-20 12:31 ` Krzysztof Kozlowski
2026-01-20 12:35 ` Abel Vesa
2026-01-30 22:38 ` Jack Pham
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=cb08a156-d905-419f-88f1-77bd136c823f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh@kernel.org \
--cc=wesley.cheng@oss.qualcomm.com \
/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