From: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
To: Andrew Halaney <ahalaney@redhat.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <neil.armstrong@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <quic_ppratap@quicinc.com>,
<quic_jackp@quicinc.com>
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sa8540-ride: Enable first port of tertiary usb controller
Date: Sat, 10 Feb 2024 16:13:51 +0530 [thread overview]
Message-ID: <b5c25274-9af0-4b3e-ade7-9a55d3cecd29@quicinc.com> (raw)
In-Reply-To: <baw3wxbdvzpkqqb6a7iut2wpt6jgzyqii5uyfkzptzt4ryjvao@4tpee6nqup5w>
> Krishna, when you make v2 can you update the wording about the USB 2.0
> mux? Maybe something like "which by default on boot is selected to mux
> to the external port on the board (with the other option being a test
> point)." instead of the wording I originally had? That way the
> information Dmitry requested here is easily accessible in the future.
>
>>
>>>
[...]
>>>>>> };
>>>>>
>>>>> Isn't gpio-hog the preferred way to describe that ?
>>>>
>>>> That depends. As this pinctrl describes board configuration, I'd agree
>>>> with Neil.
>>>
>>> I unfortunately don't have the experience with gpio-hog to weigh in
>>> here, but wouldn't be opposed to Krishna switching it if that's what's
>>> recommended for this type of thing.
>>
>> Quoting gpio.txt:
>>
>> The GPIO chip may contain GPIO hog definitions. GPIO hogging is a mechanism
>> providing automatic GPIO request and configuration as part of the
>> gpio-controller's driver probe function.
>>
>> See sdm845-pinctrl.yaml for an example of the gpio-hog node.
>
> Thanks, that seems like the way to go. Krishna please take note of this
> for v2!
>
Hi Andrew,
Can you help test the following patch. It is just an add-on to your
original one. I don't have a SA8540P Ride at the moment and getting one
might take time. Incase you can confirm this patch is working. I can
push v2 of this series.
diff --git
a/Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-tlmm.yaml
b/Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-tlmm.yaml
index ed344deaf8b9..aa42ac5a3197 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-tlmm.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-tlmm.yaml
@@ -36,6 +36,10 @@ patternProperties:
$ref: "#/$defs/qcom-sc8280xp-tlmm-state"
additionalProperties: false
+ "-hog(-[0-9]+)?$":
+ required:
+ - gpio-hog
+
$defs:
qcom-sc8280xp-tlmm-state:
type: object
diff --git a/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
b/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
index b04f72ec097c..aa0cec0b4cc2 100644
--- a/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
+++ b/arch/arm64/boot/dts/qcom/sa8540p-ride.dts
@@ -503,6 +503,18 @@ &usb_2_qmpphy0 {
status = "okay";
};
+&usb_2 {
+ pinctrl-0 = <&usb2_en_state>;
+ pinctrl-names = "default";
+
+ status = "okay";
+};
+
+&usb_2_dwc3 {
+ phy-names = "usb2-port0", "usb3-port0";
+ phys = <&usb_2_hsphy0>, <&usb_2_qmpphy0>;
+};
+
&xo_board_clk {
clock-frequency = <38400000>;
};
@@ -655,4 +667,19 @@ wake-pins {
bias-pull-up;
};
};
+
+ usb2-en-hog {
+ gpio-hog;
+ gpios = <24 GPIO_ACTIVE_LOW>;
+ output-low;
+ };
+
+ usb2_en_state: usb2-en-state {
+ /* TS3USB221A USB2.0 mux select */
+ pins = "gpio24";
+ function = "gpio";
+ drive-strength = <2>;
+ bias-disable;
+ output-low;
+ };
Regards,
Krishna,
next prev parent reply other threads:[~2024-02-10 10:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 11:47 [PATCH 0/3] Add DT support for Multiport controller on SC8280XP Krishna Kurapati
2024-02-06 11:47 ` [PATCH 1/3] arm64: dts: qcom: sc8280xp: Add multiport controller node for SC8280 Krishna Kurapati
2024-02-06 11:47 ` [PATCH 2/3] arm64: dts: qcom: sa8295p: Enable tertiary controller and its 4 USB ports Krishna Kurapati
2024-02-06 12:13 ` Dmitry Baryshkov
2024-02-06 12:28 ` Krishna Kurapati PSSNV
2024-02-06 13:24 ` Dmitry Baryshkov
2024-02-08 2:40 ` Krishna Kurapati PSSNV
2024-02-08 4:41 ` Dmitry Baryshkov
2024-02-08 4:48 ` Krishna Kurapati PSSNV
2024-02-08 5:07 ` Dmitry Baryshkov
2024-02-08 9:07 ` Krishna Kurapati PSSNV
2024-02-08 9:13 ` Krzysztof Kozlowski
2024-02-09 2:41 ` Bjorn Andersson
2024-02-09 5:15 ` Krishna Kurapati PSSNV
2024-02-06 11:47 ` [PATCH 3/3] arm64: dts: qcom: sa8540-ride: Enable first port of tertiary usb controller Krishna Kurapati
2024-02-06 13:27 ` neil.armstrong
2024-02-06 13:30 ` Dmitry Baryshkov
2024-02-07 0:09 ` Andrew Halaney
2024-02-07 1:32 ` Dmitry Baryshkov
2024-02-08 17:14 ` Andrew Halaney
2024-02-10 10:43 ` Krishna Kurapati PSSNV [this message]
2024-02-10 11:30 ` Dmitry Baryshkov
2024-02-12 19:17 ` Andrew Halaney
2024-02-13 5:11 ` Krishna Kurapati PSSNV
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=b5c25274-9af0-4b3e-ade7-9a55d3cecd29@quicinc.com \
--to=quic_kriskura@quicinc.com \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_ppratap@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
all inboxes | Powered by JetHome®