[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240906144905.591508-1-o.rempel@pengutronix.de>
Date: Fri, 6 Sep 2024 16:49:05 +0200
From: Oleksij Rempel <o.rempel@...gutronix.de>
To: Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>,
kernel@...gutronix.de,
linux-kernel@...r.kernel.org,
netdev@...r.kernel.org,
Russell King <linux@...linux.org.uk>,
devicetree@...r.kernel.org
Subject: [PATCH v1] dt-bindings: net: ethernet-phy: Add forced-master/slave properties for SPE PHYs
Add two new properties, `forced-master` and `forced-slave`, to the
ethernet-phy binding. These properties are intended for Single Pair
Ethernet (1000/100/10Base-T1) PHYs, where each PHY and product may have
a predefined link role (master or slave). Typically, these roles are set
by hardware strap pins, but in some cases, device tree configuration is
necessary.
Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
---
.../devicetree/bindings/net/ethernet-phy.yaml | 22 +++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
index d9b62741a2259..af7a1eb6ceff6 100644
--- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
@@ -158,6 +158,28 @@ properties:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
+ forced-master:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ If set, forces the PHY to operate as a master. This is used in Single Pair
+ Ethernet (1000/100/10Base-T1) where each PHY and product has a predefined
+ link role (master or slave). This property is board-specific, as the role
+ is usually configured by strap pins but can be set through the device tree
+ if needed.
+ This property is mutually exclusive with 'forced-slave'; only one of them
+ should be used.
+
+ forced-slave:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ If set, forces the PHY to operate as a slave. This is used in Single Pair
+ Ethernet (1000/100/10Base-T1) where each PHY and product has a predefined
+ link role (master or slave). This property is board-specific, as the role
+ is usually configured by strap pins but can be set through the device tree
+ if needed.
+ This property is mutually exclusive with 'forced-master'; only one of them
+ should be used.
+
pses:
$ref: /schemas/types.yaml#/definitions/phandle-array
maxItems: 1
--
2.39.2
Powered by blists - more mailing lists