From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andyshrk@163.com>
Cc: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andyshrk@163.com>
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator for Cool Pi CM5 EVB
Date: Sat, 27 Jan 2024 11:36:40 +0100 [thread overview]
Message-ID: <2798389.3c9HiEOlIg@diego> (raw)
In-Reply-To: <20240127092034.887085-3-andyshrk@163.com>
Hi Andy,
Am Samstag, 27. Januar 2024, 10:20:33 CET schrieb Andy Yan:
> According to the schematic, this regulator is used both for USB30 and
> USB20, so give it a more appropriate name.
I don't have the schematics, so I'll need you to answer this, but what
is the regulator called _in_ the schematics?
I.e. we want regulators to really be named the same as in the schematic
so people can look up thing from the dts in the schematics and the other
way around too.
Thanks
Heiko
> Fixes: 791c154c3982 ("arm64: dts: rockchip: Add support for rk3588 based board Cool Pi CM5 EVB")
> Signed-off-by: Andy Yan <andyshrk@163.com>
> ---
>
> arch/arm64/boot/dts/rockchip/rk3588-coolpi-cm5-evb.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-coolpi-cm5-evb.dts b/arch/arm64/boot/dts/rockchip/rk3588-coolpi-cm5-evb.dts
> index 1b5681fe0471..5f42f1065d73 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-coolpi-cm5-evb.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-coolpi-cm5-evb.dts
> @@ -84,7 +84,7 @@ vcc3v3_lcd: vcc3v3-lcd-regulator {
> vin-supply = <&vcc3v3_sys>;
> };
>
> - vcc5v0_usb30_host: vcc5v0-usb30-host-regulator {
> + vcc5v0_usb_host: vcc5v0-usb-host-regulator {
> compatible = "regulator-fixed";
> regulator-name = "vcc5v0_host";
> regulator-boot-on;
> @@ -200,12 +200,12 @@ &u2phy3 {
> };
>
> &u2phy2_host {
> - phy-supply = <&vcc5v0_usb30_host>;
> + phy-supply = <&vcc5v0_usb_host>;
> status = "okay";
> };
>
> &u2phy3_host {
> - phy-supply = <&vcc5v0_usb30_host>;
> + phy-supply = <&vcc5v0_usb_host>;
> status = "okay";
> };
>
>
next prev parent reply other threads:[~2024-01-27 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 9:20 [PATCH 1/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi 4B Andy Yan
2024-01-27 9:20 ` [PATCH 2/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi CM5 EVB Andy Yan
2024-01-27 13:07 ` Dragan Simic
2024-01-27 9:20 ` [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator " Andy Yan
2024-01-27 10:36 ` Heiko Stübner [this message]
2024-01-27 12:15 ` Andy Yan
2024-01-27 13:09 ` Dragan Simic
2024-01-31 12:21 ` Andy Yan
2024-01-31 14:24 ` Heiko Stübner
2024-01-27 9:20 ` [PATCH 4/4] arm64: dts: rockchip: Fix the num-lanes of pcie3x4 on " Andy Yan
2024-01-27 13:07 ` [PATCH 1/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi 4B Dragan Simic
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=2798389.3c9HiEOlIg@diego \
--to=heiko@sntech.de \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).