From: Konrad Dybcio <konradybcio@gmail.com>
To: Song Xue <quic_songxue@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krishna Kurapati <quic_kriskura@quicinc.com>,
Konrad Dybcio <quic_kdybcio@quicinc.com>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: x1e80100: Add USB Multiport controller
Date: Wed, 14 Aug 2024 12:24:29 +0200 [thread overview]
Message-ID: <3077d600-c570-407a-87eb-6926a67636f9@gmail.com> (raw)
In-Reply-To: <21fffb71-d559-4973-8028-d9c9b9f67001@quicinc.com>
On 14.08.2024 12:08 PM, Song Xue wrote:
>
> On 8/9/2024 9:18 PM, Konrad Dybcio wrote:
>> X1E80100 has a multiport controller with 2 HS (eUSB) and 2 SS PHYs
>> attached to it. It's commonly used for USB-A ports and internally
>> routed devices. Configure it to support such functionality.
>>
>> Signed-off-by: Konrad Dybcio<konrad.dybcio@linaro.org>
>> ---
[...]
>> +
>> + phys = <&usb_mp_hsphy0>, <&usb_mp_qmpphy0>,
>> + <&usb_mp_hsphy1>, <&usb_mp_qmpphy1>;
>> + phy-names = "usb2-0", "usb3-0",
>> + "usb2-1", "usb3-1";
>> + dr_mode = "host";
>
> Why do we add the dr_mode definition in dtsi file rather than in corresponding board dts file? Could we follow the node "usb_1_ss1_dwc3" in x1e80100-crd.dtsi?
That is because the MP controller is host-only and it doesn't make sense
to ensure the OS of that in each board file separately. That's also how
it's done on other platforms with a MP controller description.
>
> BTW, how do we verify the function of multiport controller?From my test on x1e80100-crd, the eusb6 which is from usb_mp_hsphy1 attaches the third-party repeater, do we need a new repeater node/driver to verify the function of eusb6?
I have a X1E Surface Laptop 7 with a USB-A port with a NXP PTN3222 in
front of it. Tested with a smoke test, with both SS and HS USB-A devices.
Konrad
next prev parent reply other threads:[~2024-08-14 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 13:18 [PATCH 0/2] X1E80100 multiport USB controller Konrad Dybcio
2024-08-09 13:18 ` [PATCH 1/2] dt-bindings: usb: qcom,dwc3: Document X1E80100 MP controller Konrad Dybcio
2024-08-10 12:47 ` Krzysztof Kozlowski
2024-08-09 13:18 ` [PATCH 2/2] arm64: dts: qcom: x1e80100: Add USB Multiport controller Konrad Dybcio
2024-08-10 12:48 ` Krzysztof Kozlowski
2024-08-13 14:09 ` Konrad Dybcio
2024-08-13 14:35 ` Krzysztof Kozlowski
2024-08-13 15:21 ` Konrad Dybcio
[not found] ` <21fffb71-d559-4973-8028-d9c9b9f67001@quicinc.com>
2024-08-14 10:24 ` Konrad Dybcio [this message]
2024-08-14 11:56 ` Song Xue
2024-08-17 11:32 ` Konrad Dybcio
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=3077d600-c570-407a-87eb-6926a67636f9@gmail.com \
--to=konradybcio@gmail.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=marijn.suijten@somainline.org \
--cc=quic_kdybcio@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_songxue@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--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