From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Abel Vesa <abel.vesa@linaro.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] arm64: dts: qcom: sm8550-mtp: Add eUSB2 repeater node
Date: Wed, 16 Nov 2022 14:28:56 +0100 [thread overview]
Message-ID: <9666803c-2f9f-04b2-9bb8-2fec8231a324@linaro.org> (raw)
In-Reply-To: <20221116132706.2852434-3-abel.vesa@linaro.org>
On 16/11/2022 14:27, Abel Vesa wrote:
> Add the PMIC eUSB2 repeater node and add the usb-repeater
> property to the eUSB2 PHY to allow it to be controlled by the
> PHY driver.
>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/sm8550-mtp.dts | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8550-mtp.dts b/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> index 757cf4f7f195..539d75c0566f 100644
> --- a/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> @@ -414,6 +414,11 @@ data-pins {
> };
> };
>
> +&pm8550b_eusb2_repeater {
Sorting is off.
Konrad
> + vdd18-supply = <&vreg_l15b_1p8>;
> + vdd3-supply = <&vreg_l5b_3p1>;
> +};
> +
> &uart7 {
> status = "okay";
> };
> @@ -429,6 +434,8 @@ &usb_1_dwc3 {
> &usb_1_hsphy {
> status = "okay";
>
> + usb-repeater = <&pm8550b_eusb2_repeater>;
> +
> vdd-supply = <&vreg_l1e_0p88>;
> vdda12-supply = <&vreg_l3e_1p2>;
> };
prev parent reply other threads:[~2022-11-16 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 13:27 [RFC PATCH 0/2] arm64: dts: qcom: sm8550: Add eUSB2 repeater Abel Vesa
2022-11-16 13:27 ` [RFC PATCH 1/2] arm64: dts: qcom: pm8550b: Add eUSB2 repeater node Abel Vesa
2022-11-16 13:27 ` [RFC PATCH 2/2] arm64: dts: qcom: sm8550-mtp: " Abel Vesa
2022-11-16 13:28 ` Konrad Dybcio [this message]
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=9666803c-2f9f-04b2-9bb8-2fec8231a324@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@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
all inboxes | Powered by JetHome®