On Mon, Sep 09, 2024 at 02:43:40PM +0200, Oleksij Rempel wrote: > Introduce a new `master-slave` string property in the ethernet-phy > binding to specify the link role for Single Pair Ethernet > (1000/100/10Base-T1) PHYs. This property supports the values > `forced-master` and `forced-slave`, which allow the PHY to operate in a > predefined role, necessary when hardware strap pins are unavailable or > wrongly set. > > Signed-off-by: Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> > --- > changes v2: > - use string property instead of multiple flags > --- > .../devicetree/bindings/net/ethernet-phy.yaml | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > index d9b62741a2259..025e59f6be6f3 100644 > --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml > +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > @@ -158,6 +158,20 @@ properties: > Mark the corresponding energy efficient ethernet mode as > broken and request the ethernet to stop advertising it. > > + master-slave: Outdated terminology and kind of vague what it is for... The usual transformation to 'controller-device' would not make much sense though. I think a better name would be "spe-link-role" or "spe-link-mode". > + $ref: /schemas/types.yaml#/definitions/string > + enum: > + - forced-master > + - forced-slave > + description: | > + Specifies the predefined link role for the PHY in Single Pair Ethernet > + (1000/100/10Base-T1). This property is required for setups where the link > + role must be assigned by the device tree due to limitations in using > + hardware strap pins. > + > + - 'forced-master': The PHY is forced to operate as a master. > + - 'forced-slave': The PHY is forced to operate as a slave. > + > pses: > $ref: /schemas/types.yaml#/definitions/phandle-array > maxItems: 1 > -- > 2.39.2 >
