From: Dragan Simic <dsimic@manjaro.org>
To: Justin Klaassen <justin@tidylabs.net>
Cc: Tianling Shen <cnsztl@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
Johan Jonker <jbx6244@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: fix u2phy1_host status for NanoPi R4S
Date: Tue, 25 Feb 2025 15:25:52 +0100 [thread overview]
Message-ID: <48c705e65cc8e8d4716b41a4a87170e3@manjaro.org> (raw)
In-Reply-To: <20250224170925.39126-1-justin@tidylabs.net>
Hello Justin,
Thanks for the patch! Please, see a few comments below.
On 2025-02-24 18:09, Justin Klaassen wrote:
> The u2phy1_host should always have the same status as usb_host1_ehci,
> otherwise the ehci driver may be initialized for a disabled usb port.
>
> Signed-off-by: Justin Klaassen <justin@tidylabs.net>
> ---
> arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
> index b1c9bd0e63ef..8d94d9f91a5c 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi
> @@ -115,7 +115,7 @@ &u2phy0_host {
> };
>
> &u2phy1_host {
> - status = "disabled";
> + phy-supply = <&vdd_5v>;
> };
>
> &uart0 {
Indeed, the rk3399-nanopi4.dtsi file, which rk3399-nanopi-r4s.dtsi
extends, enables u2phy1_host, usb_host1_ehci and usb_host1_ohci,
so disabling u2phy1_host in rk3399-nanopi-r4s.dtsi makes no sense.
After checking the NanoPi R4S schematic, I can confirm that the
phy-supply references the right regulator. There are some strange
things in the schematic, but they're unrelated to this patch.
However, there should be a v2 of this patch with the proper Fixes
and CC: stable tags, so this bugfix also gets propagated into the
long-term kernels. Please, feel free to also include
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
next prev parent reply other threads:[~2025-02-25 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:09 Justin Klaassen
2025-02-25 14:25 ` Dragan Simic [this message]
2025-02-25 17:03 ` [PATCH v2] " Justin Klaassen
2025-02-27 13:37 ` Heiko Stuebner
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=48c705e65cc8e8d4716b41a4a87170e3@manjaro.org \
--to=dsimic@manjaro.org \
--cc=cnsztl@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=justin@tidylabs.net \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
all inboxes | Powered by JetHome®