netdev - Re: [net-next RFC PATCH v2 1/3] dt-bindings: net: dsa: Add Airoha AN8855 Gigabit Switch documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <67192f00.7b0a0220.343b2b.9836@mx.google.com>
Date: Wed, 23 Oct 2024 19:14:37 +0200
From: Christian Marangi <ansuelsmth@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Florian Fainelli <f.fainelli@...il.com>,
	Vladimir Oltean <olteanv@...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>,
	Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	Matthias Brugger <matthias.bgg@...il.com>,
	AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
	linux-arm-kernel@...ts.infradead.org,
	linux-mediatek@...ts.infradead.org, netdev@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [net-next RFC PATCH v2 1/3] dt-bindings: net: dsa: Add Airoha
 AN8855 Gigabit Switch documentation

On Wed, Oct 23, 2024 at 07:08:57PM +0200, Andrew Lunn wrote:
> > +  airoha,base_smi_address:
> > +    $ref: /schemas/types.yaml#/definitions/uint32
> > +    description:
> > +      Configure and change the base switch PHY address to a new address on
> > +      the bus.
> > +      On reset, the switch PHY address is ALWAYS 1.
> > +    default: 1
> > +    maximum: 31
> 
> Given that this is a 5 port switch, what happens if i pick a value
> greater than 31 - 5 ?

The PHY at those address won't be reachable, I didn't think of this, you
are right.

> 
> Do you have a real use case for this? A board which requires the PHYs
> get shifted from the default of 1? Vendors have all sorts of bells and
> whistles which we never use. If its not needed, i would not add it,
> until it is actually needed, if ever.

Well the first case that comes to mind is multiple switch and conflict.
I have no idea if there are hw strap to configure this so I assume if a
SoC have 2 switch (maybe of the same type), this permits to configure
them (with reset pin and deasserting them once the base address is
correctly configured)

But yes totally ok to drop this if too strange... I assume it's problematic
that PHY change at runtime.

> 
> > +  mdio:
> > +    $ref: /schemas/net/mdio.yaml#
> > +    unevaluatedProperties: false
> > +    description:
> > +      Define the relative address of the internal PHY for each port.
> > +
> > +      Each reg for the PHY is relative to the switch base PHY address.
> 
> Which is not the usual meaning of reg.
> 
> > +            mdio {
> > +                #address-cells = <1>;
> > +                #size-cells = <0>;
> > +
> > +                internal_phy0: phy@0 {
> > +                    reg = <0>;
> 
> So given that airoha,base_smi_address defaults to 1, this is actually
> address 1 on the MDIO bus?
>

Yes correct. One problem I had was that moving this outside the swich
cause panic as it does conflict with the switch PHY address...

-- 
	Ansuel