.../devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml | 3 +-- Documentation/devicetree/bindings/net/ethernet-phy.yaml | 3 --- Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml | 3 +-- Documentation/devicetree/bindings/net/renesas,ether.yaml | 3 +-- Documentation/devicetree/bindings/net/renesas,etheravb.yaml | 3 +-- 5 files changed, 4 insertions(+), 11 deletions(-)
From: Biju Das <biju.das.jz@bp.renesas.com>
Drop the ethernet-phy-ieee802.3-c22 compatible string from ethernet PHY
bindings and their examples. The c22 fallback is implicitly assumed for
PHY ID-based compatible strings and does not need to be stated explicitly,
unlike c45 which requires opt-in.
Remove the c22 pattern from the ethernet-phy.yaml schema and update
examples in amlogic,g12a-mdio-mux, mscc-phy-vsc8531, renesas,ether,
and renesas,etheravb bindings accordingly.
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
---
.../devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml | 3 +--
Documentation/devicetree/bindings/net/ethernet-phy.yaml | 3 ---
Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml | 3 +--
Documentation/devicetree/bindings/net/renesas,ether.yaml | 3 +--
Documentation/devicetree/bindings/net/renesas,etheravb.yaml | 3 +--
5 files changed, 4 insertions(+), 11 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml b/Documentation/devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml
index ec5c038ce6a0..e9e575fab62c 100644
--- a/Documentation/devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml
+++ b/Documentation/devicetree/bindings/net/amlogic,g12a-mdio-mux.yaml
@@ -69,8 +69,7 @@ examples:
#size-cells = <0>;
ethernet-phy@8 {
- compatible = "ethernet-phy-id0180.3301",
- "ethernet-phy-ieee802.3-c22";
+ compatible = "ethernet-phy-id0180.3301";
interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>;
reg = <8>;
max-speed = <100>;
diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
index 58634fee9fc4..d622e73a89ff 100644
--- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
@@ -47,9 +47,6 @@ properties:
second group of digits is the Phy Identifier 2 register,
this is the chip vendor OUI bits 19:24, followed by 10
bits of a vendor specific ID.
- - items:
- - pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
- - const: ethernet-phy-ieee802.3-c22
- items:
- pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
- const: ethernet-phy-ieee802.3-c45
diff --git a/Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml b/Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml
index 0afbd0ff126f..5e5dea7987e7 100644
--- a/Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml
+++ b/Documentation/devicetree/bindings/net/mscc-phy-vsc8531.yaml
@@ -32,7 +32,6 @@ properties:
- enum:
- ethernet-phy-id0007.0570 # VSC8531
- ethernet-phy-id0007.0772 # VSC8541
- - const: ethernet-phy-ieee802.3-c22
vsc8531,vddmac:
$ref: /schemas/types.yaml#/definitions/uint32
@@ -120,7 +119,7 @@ examples:
#size-cells = <0>;
ethernet-phy@0 {
- compatible = "ethernet-phy-id0007.0772", "ethernet-phy-ieee802.3-c22";
+ compatible = "ethernet-phy-id0007.0772";
reg = <0>;
vsc8531,vddmac = <3300>;
vsc8531,edge-slowdown = <7>;
diff --git a/Documentation/devicetree/bindings/net/renesas,ether.yaml b/Documentation/devicetree/bindings/net/renesas,ether.yaml
index f0a52f47f95a..dd7187f12a67 100644
--- a/Documentation/devicetree/bindings/net/renesas,ether.yaml
+++ b/Documentation/devicetree/bindings/net/renesas,ether.yaml
@@ -121,8 +121,7 @@ examples:
#size-cells = <0>;
phy1: ethernet-phy@1 {
- compatible = "ethernet-phy-id0022.1537",
- "ethernet-phy-ieee802.3-c22";
+ compatible = "ethernet-phy-id0022.1537";
reg = <1>;
interrupt-parent = <&irqc0>;
interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
diff --git a/Documentation/devicetree/bindings/net/renesas,etheravb.yaml b/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
index 1e00ef5b3acd..6aea1acaaa59 100644
--- a/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
+++ b/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
@@ -364,8 +364,7 @@ examples:
#size-cells = <0>;
phy0: ethernet-phy@0 {
- compatible = "ethernet-phy-id0022.1622",
- "ethernet-phy-ieee802.3-c22";
+ compatible = "ethernet-phy-id0022.1622";
rxc-skew-ps = <1500>;
reg = <0>;
interrupt-parent = <&gpio2>;
--
2.43.0On Fri, Mar 13, 2026 at 01:06:21PM +0000, Biju wrote: > From: Biju Das <biju.das.jz@bp.renesas.com> > > Drop the ethernet-phy-ieee802.3-c22 compatible string from ethernet PHY > bindings and their examples. The c22 fallback is implicitly assumed for > PHY ID-based compatible strings and does not need to be stated explicitly, > unlike c45 which requires opt-in. > > Remove the c22 pattern from the ethernet-phy.yaml schema and update > examples in amlogic,g12a-mdio-mux, mscc-phy-vsc8531, renesas,ether, > and renesas,etheravb bindings accordingly. This will introduce a ton of warnings in .dts files which I don't think anyone wants to go fix. While I think it's redundant to have the c22 (or c45) fallback as it isn't really useful on its own, I think we are too far down that path. You need a custom 'select' in all the schemas that have a c22 compatible to exclude it from matching. Rob
On Fri, 13 Mar 2026 13:06:21 +0000 Biju wrote: > From: Biju Das <biju.das.jz@bp.renesas.com> > > Drop the ethernet-phy-ieee802.3-c22 compatible string from ethernet PHY > bindings and their examples. The c22 fallback is implicitly assumed for > PHY ID-based compatible strings and does not need to be stated explicitly, > unlike c45 which requires opt-in. > > Remove the c22 pattern from the ethernet-phy.yaml schema and update > examples in amlogic,g12a-mdio-mux, mscc-phy-vsc8531, renesas,ether, > and renesas,etheravb bindings accordingly. Maybe a noob question but why are you not updating all the other ones? $ git grep --files-with-matches 'ethernet-phy-ieee802.3-c22' -- \ Documentation/devicetree/bindings/net/ | \ wc -l 16
© 2016 - 2026 Red Hat, Inc.