From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, khilman@baylibre.com,
neil.armstrong@linaro.org, jbrunet@baylibre.com,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH v2 5/6] arm64: dts: meson-g12a: Fix internal Ethernet PHY unit name
Date: Wed, 11 Jan 2023 22:13:49 +0100 [thread overview]
Message-ID: <20230111211350.1461860-6-martin.blumenstingl@googlemail.com> (raw)
In-Reply-To: <20230111211350.1461860-1-martin.blumenstingl@googlemail.com>
Documentation/devicetree/bindings/net/ethernet-phy.yaml defines that the
node name for Ethernet PHYs should match the following pattern:
^ethernet-phy(@[a-f0-9]+)?$
Replace the underscore with a hyphen to adhere to this binding.
Fixes: 280c17df8fbf ("arm64: dts: meson: g12a: add mdio multiplexer")
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
---
changes from v1 -> v2:
- new patch
arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
index 9dbd50820b1c..c95cf3afc666 100644
--- a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
+++ b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
@@ -1694,7 +1694,7 @@ int_mdio: mdio@1 {
#address-cells = <1>;
#size-cells = <0>;
- internal_ephy: ethernet_phy@8 {
+ internal_ephy: ethernet-phy@8 {
compatible = "ethernet-phy-id0180.3301",
"ethernet-phy-ieee802.3-c22";
interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>;
--
2.39.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-01-11 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 21:13 [PATCH v2 0/6] arm64: dts: small .dts fixes Martin Blumenstingl
2023-01-11 21:13 ` [PATCH v2 1/6] arm64: dts: meson-gxl: jethub-j80: Fix WiFi MAC address node Martin Blumenstingl
2023-01-13 7:58 ` neil.armstrong
2023-01-11 21:13 ` [PATCH v2 2/6] arm64: dts: meson-gxl: jethub-j80: Fix Bluetooth MAC node name Martin Blumenstingl
2023-01-13 7:58 ` neil.armstrong
2023-01-11 21:13 ` [PATCH v2 3/6] arm64: dts: meson-axg: jethub-j1xx: Fix MAC address node names Martin Blumenstingl
2023-01-13 7:59 ` neil.armstrong
2023-01-11 21:13 ` [PATCH v2 4/6] arm64: dts: meson-gx: Fix Ethernet MAC address unit name Martin Blumenstingl
2023-01-13 7:59 ` neil.armstrong
2023-01-13 7:59 ` neil.armstrong
2023-01-11 21:13 ` Martin Blumenstingl [this message]
2023-01-13 7:59 ` [PATCH v2 5/6] arm64: dts: meson-g12a: Fix internal Ethernet PHY " neil.armstrong
2023-01-11 21:13 ` [PATCH v2 6/6] arm64: dts: meson-gx: Fix the SCPI DVFS node name and unit address Martin Blumenstingl
2023-01-13 7:59 ` neil.armstrong
2023-01-13 8:03 ` [PATCH v2 0/6] arm64: dts: small .dts fixes Neil Armstrong
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=20230111211350.1461860-6-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.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®