From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, bhupesh.linux@gmail.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski@linaro.org, andersson@kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm6115: Move USB node's 'maximum-speed' and 'dr_mode' properties to dts
Date: Tue, 13 Dec 2022 13:39:32 +0100 [thread overview]
Message-ID: <739feff0-914b-c565-bd16-5099ceda49a9@linaro.org> (raw)
In-Reply-To: <20221213123823.455731-3-bhupesh.sharma@linaro.org>
On 13.12.2022 13:38, Bhupesh Sharma wrote:
> Normally the 'maximum-speed' and 'dr_mode' properties
> of a USB controller + port is dependent on the type of
> the ports, regulators and mode change interrupt routing
> available on the board(s).
>
> So, move the same from the sm6115 dtsi file to respective
> board file(s).
>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts | 5 +++++
> arch/arm64/boot/dts/qcom/sm6115.dtsi | 2 --
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts b/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts
> index fa57f4bf58256..3f39f25e0721e 100644
> --- a/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts
> +++ b/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts
> @@ -229,6 +229,11 @@ &usb {
> status = "okay";
> };
>
> +&usb_dwc3 {
> + maximum-speed = "high-speed";
> + dr_mode = "peripheral";
> +};
> +
> &usb_hsphy {
> vdd-supply = <&vreg_l4a>;
> vdda-pll-supply = <&vreg_l12a>;
> diff --git a/arch/arm64/boot/dts/qcom/sm6115.dtsi b/arch/arm64/boot/dts/qcom/sm6115.dtsi
> index b5f7480c2e713..e4ce135264f3d 100644
> --- a/arch/arm64/boot/dts/qcom/sm6115.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm6115.dtsi
> @@ -1031,8 +1031,6 @@ usb_dwc3: usb@4e00000 {
> snps,has-lpm-erratum;
> snps,hird-threshold = /bits/ 8 <0x10>;
> snps,usb3_lpm_capable;
> - maximum-speed = "high-speed";
> - dr_mode = "peripheral";
> };
> };
>
next prev parent reply other threads:[~2022-12-13 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 12:38 [PATCH 0/3] arm64: dts: sm6115: Add USB SS qmp phy node and perform some cleanups Bhupesh Sharma
2022-12-13 12:38 ` [PATCH 1/3] arm64: dts: qcom: sm6115: Cleanup USB node names Bhupesh Sharma
2022-12-13 12:39 ` Konrad Dybcio
2022-12-13 12:51 ` Krzysztof Kozlowski
2022-12-13 18:49 ` Bhupesh Sharma
2022-12-13 12:38 ` [PATCH 2/3] arm64: dts: qcom: sm6115: Move USB node's 'maximum-speed' and 'dr_mode' properties to dts Bhupesh Sharma
2022-12-13 12:39 ` Konrad Dybcio [this message]
2022-12-13 12:38 ` [PATCH 3/3] arm64: dts: qcom: sm6115: Add USB SS qmp phy node Bhupesh Sharma
2022-12-13 12:49 ` Konrad Dybcio
2022-12-13 22:18 ` Dmitry Baryshkov
2022-12-14 4:43 ` Bhupesh Sharma
2022-12-13 12:56 ` Krzysztof Kozlowski
2022-12-13 18:52 ` Bhupesh Sharma
2022-12-13 18:54 ` Konrad Dybcio
2022-12-13 18:59 ` Krzysztof Kozlowski
2022-12-14 5:20 ` Bhupesh Sharma
2022-12-14 9:56 ` 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=739feff0-914b-c565-bd16-5099ceda49a9@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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