On Wed, Aug 21, 2024 at 01:46:30PM +0100, Daniel Golle wrote: > Usually the MDI pair order reversal configuration is defined by > bootstrap pin MDI_CFG. Some designs, however, require overriding the MDI > pair order and force either normal or reverse order. Is that a PC way of saying that someone messed up and wired the pins incorrectly? A concrete example of why this is required would be good ;) > > Add properties 'marvell,force-mdi-order-normal' and > 'marvell,force-mdi-order-reverse' for that purpose. > > Signed-off-by: Daniel Golle <daniel@xxxxxxxxxxxxxx> > --- > .../devicetree/bindings/net/marvell,aquantia.yaml | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/marvell,aquantia.yaml b/Documentation/devicetree/bindings/net/marvell,aquantia.yaml > index 9854fab4c4db0..c82d0be48741d 100644 > --- a/Documentation/devicetree/bindings/net/marvell,aquantia.yaml > +++ b/Documentation/devicetree/bindings/net/marvell,aquantia.yaml > @@ -48,6 +48,16 @@ properties: > firmware-name: > description: specify the name of PHY firmware to load > > + marvell,force-mdi-order-normal: > + type: boolean > + description: > + force normal order of MDI pairs, overriding MDI_CFG bootstrap pin. > + > + marvell,force-mdi-order-reverse: > + type: boolean > + description: > + force reverse order of MDI pairs, overriding MDI_CFG bootstrap pin. These properties are mutually exclusive, right? If so, the binding should enforce that. Thanks, Conor. > + > nvmem-cells: > description: phandle to the firmware nvmem cell > maxItems: 1 > -- > 2.46.0
Attachment:
signature.asc
Description: PGP signature
