From: Anand Moon <linux.amoon@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (moderated list:ARM/Amlogic
Meson SoC support),
linux-amlogic@lists.infradead.org (open list:ARM/Amlogic Meson
SoC support), linux-kernel@vger.kernel.org (open list)
Cc: Anand Moon <linux.amoon@gmail.com>, Wayne Schroeder <raz@chewies.net>
Subject: [PATCH v3 2/2] arm64: dts: amlogic: Adjust USB PHY power supply references
Date: Thu, 22 May 2025 22:55:32 +0530 [thread overview]
Message-ID: <20250522172535.302064-2-linux.amoon@gmail.com> (raw)
In-Reply-To: <20250522172535.302064-1-linux.amoon@gmail.com>
According to the Odroid-N2 schematics, the micro-USB phy is powered
via a gpio-controlled regulator PWREN, updates the phy-supply to
correctly assign the power supply for usb2_phy.
Additionally, the USB3 combo port, which connects to the onboard
4-port USB hub, is powered by the main VCC_5V rail. Updated the
phy-supply to correctly assign vcc_5v for the USB controller node.
These changes ensure accurate power supply configuration for
USB components, improving hardware compatibility and power management.
Signed-off-by: Anand Moon <linux.amoon@gmail.com>
---
new patch
---
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi | 2 +-
arch/arm64/boot/dts/amlogic/meson-g12b-odroid.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi
index ad959f8bc1acd..9d63ab82302eb 100644
--- a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi
+++ b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi
@@ -310,7 +310,7 @@ &toacodec {
};
&usb {
- vbus-supply = <&usb_pwr_en>;
+ phy-supply = <&vcc_5v>;
};
&usb2_phy1 {
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid.dtsi
index 7e8964bacfce7..b105a8ae2fec6 100644
--- a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid.dtsi
+++ b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid.dtsi
@@ -437,5 +437,5 @@ &usb {
};
&usb2_phy0 {
- phy-supply = <&vcc_5v>;
+ phy-supply = <&usb_pwr_en>;
};
--
2.49.0
next prev parent reply other threads:[~2025-05-22 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 17:25 [PATCH v3 1/2] arm64: dts: amlogic: Update USB hub power and reset properties Anand Moon
2025-05-22 17:25 ` Anand Moon [this message]
2025-05-23 19:16 ` Rob Herring (Arm)
2025-05-28 7:33 ` Anand Moon
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=20250522172535.302064-2-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=raz@chewies.net \
--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;
as well as URLs for NNTP newsgroup(s).