From: Song Xue <quic_songxue@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@quicinc.com>,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: Enable secondary USB controller on QCS615 Ride
Date: Fri, 13 Dec 2024 14:59:45 +0800 [thread overview]
Message-ID: <4476bfe9-41fb-4ec3-b352-624fba75cf3f@quicinc.com> (raw)
In-Reply-To: <cc3edfc6-f53c-401b-b766-f8e560eb24b9@oss.qualcomm.com>
On 12/13/2024 2:14 AM, Konrad Dybcio wrote:
> On 11.12.2024 9:26 AM, Song Xue wrote:
>> From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
>>
>> Enable secondary USB controller on QCS615 Ride platform. The secondary
>> USB controller is made "host", as it is a Type-A port.
>>
>> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
>> Co-developed-by: Song Xue <quic_songxue@quicinc.com>
>> Signed-off-by: Song Xue <quic_songxue@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs615-ride.dts | 28 ++++++++++++++++++++++++++++
>> 1 file changed, 28 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs615-ride.dts b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> index f41319ff47b983d771da52775fa78b4385c4e532..26ce0496d13ccbfea392c6d50d9edcab85fbc653 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> +++ b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> @@ -203,6 +203,15 @@ &gcc {
>> <&sleep_clk>;
>> };
>>
>> +&pm8150_gpios {
>> + usb2_en_state: usb2-en-state {
>> + pins = "gpio10";
>> + function = "normal";
>> + output-high;
>> + power-source = <0>;
>> + };
>
> Does this go to an enable pin of a vreg / switch?
Thanks for comment.
We go to enable the pin of PMIC chip. The pin of PMIC is connecting to
host-enable pin of USB converter. Need pin of PMIC chip to be high
level, when USB is as host mode.
>
> I think we settled on describing such cases as fixed regulators
> (that are always-on for now) - would you remember, +Dmitry?
>
> The rest looks good.
>
> Konrad
next prev parent reply other threads:[~2024-12-13 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 8:26 [PATCH v2 0/2] arm64: dts: qcom: Add DT support for secondary USB on QCS615 Song Xue
2024-12-11 8:26 ` [PATCH v2 1/2] arm64: dts: qcom: Add support for secondary USB node " Song Xue
2024-12-12 18:10 ` Konrad Dybcio
2024-12-13 6:12 ` Krishna Kurapati
2024-12-13 7:54 ` Krzysztof Kozlowski
2024-12-13 10:37 ` Song Xue
2024-12-11 8:26 ` [PATCH v2 2/2] arm64: dts: qcom: Enable secondary USB controller on QCS615 Ride Song Xue
2024-12-12 18:14 ` Konrad Dybcio
2024-12-13 5:20 ` Dmitry Baryshkov
2024-12-13 11:42 ` Krishna Kurapati
2024-12-13 6:59 ` Song Xue [this message]
2024-12-13 8:12 ` Dmitry Baryshkov
2024-12-13 11:03 ` Song Xue
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=4476bfe9-41fb-4ec3-b352-624fba75cf3f@quicinc.com \
--to=quic_songxue@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--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