Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Komal Bajaj <quic_kbajaj@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Amrit Anand <quic_amrianan@quicinc.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: qdu1000-idp: enable USB nodes
Date: Tue, 12 Mar 2024 01:04:00 +0100	[thread overview]
Message-ID: <e787706d-b5ef-40bd-9fa8-fed784a9d7b7@linaro.org> (raw)
In-Reply-To: <CAA8EJpqMWBWAEUCiJXm0x7zjZYbP8SkRDgu+w+goYjB=8JBN0A@mail.gmail.com>



On 3/11/24 13:14, Dmitry Baryshkov wrote:
> On Mon, 11 Mar 2024 at 14:10, Komal Bajaj <quic_kbajaj@quicinc.com> wrote:
>>
>> Enable both USB controllers and associated hsphy and qmp phy nodes
>> on QDU1000 IDP.
>>
>> Co-developed-by: Amrit Anand <quic_amrianan@quicinc.com>
>> Signed-off-by: Amrit Anand <quic_amrianan@quicinc.com>
>> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
>> ---
>>   arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 24 ++++++++++++++++++++++++
>>   1 file changed, 24 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> index 89b84fb0f70a..126bc71afd90 100644
>> --- a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> +++ b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> @@ -500,3 +500,27 @@ &tlmm {
>>   &uart7 {
>>          status = "okay";
>>   };
>> +
>> +&usb_1 {
>> +       status = "okay";
>> +};
>> +
>> +&usb_1_dwc3 {
>> +       dr_mode = "peripheral";
> 
> Are these ports really peripheral-only?
> 
>> +       maximum-speed = "high-speed";

More importantly, are these ports really HS-only?

Konrad

  reply	other threads:[~2024-03-12  0:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 12:08 [PATCH 0/3] Add devicetree support of USB for QDU/QRU1000 Komal Bajaj
2024-03-11 12:08 ` [PATCH 1/3] arm64: dts: qcom: qdu1000: Add USB3 and PHY support Komal Bajaj
2024-03-11 16:32   ` Krzysztof Kozlowski
2024-03-19  8:32     ` Komal Bajaj
2024-03-11 12:08 ` [PATCH 2/3] arm64: dts: qcom: qdu1000-idp: enable USB nodes Komal Bajaj
2024-03-11 12:14   ` Dmitry Baryshkov
2024-03-12  0:04     ` Konrad Dybcio [this message]
2024-03-19  8:34       ` Komal Bajaj
2024-03-11 12:08 ` [PATCH 3/3] arm64: dts: qcom: qru1000-idp: " Komal Bajaj
2024-03-11 14:23 ` [PATCH 0/3] Add devicetree support of USB for QDU/QRU1000 Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2024-03-19  9:10 Komal Bajaj
2024-03-19  9:10 ` [PATCH 2/3] arm64: dts: qcom: qdu1000-idp: enable USB nodes Komal Bajaj
2024-03-19  9:52   ` Dmitry Baryshkov
2024-04-01 22:55     ` Bjorn Andersson
2024-04-03  7:50       ` Krishna Kurapati PSSNV
2024-04-03 15:52         ` Dmitry Baryshkov

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=e787706d-b5ef-40bd-9fa8-fed784a9d7b7@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_amrianan@quicinc.com \
    --cc=quic_kbajaj@quicinc.com \
    --cc=robh+dt@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