[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f76df98e-f743-4dc2-9f10-93b97f69addb@lunn.ch>
Date: Thu, 21 Aug 2025 15:42:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Yangfl <mmyangfl@...il.com>
Cc: netdev@...r.kernel.org, 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>, Simon Horman <horms@...nel.org>,
Russell King <linux@...linux.org.uk>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [net-next v5 1/3] dt-bindings: net: dsa: yt921x: Add Motorcomm
YT921x switch support
On Thu, Aug 21, 2025 at 08:50:18PM +0800, Yangfl wrote:
> On Thu, Aug 21, 2025 at 8:41 PM Andrew Lunn <andrew@...n.ch> wrote:
> >
> > > + switch@1d {
> > > + compatible = "motorcomm,yt9215";
> > > + /* default 0x1d, alternate 0x0 */
> > > + reg = <0x1d>;
> >
> > Just curious, what does alternative 0x0 mean? Does this switch have
> > only one strapping pin for address, so it either uses address 0x1d or
> > 0x0?
> >
> > Andrew
>
> Yes. I've seen this approach on other chips (offering two MDIO
> phyaddrs), so this should be a common practice.
If it only supports two addresses, you could add a constrain in the
binding that reg is [0x0, 0x1d].
Andrew
Powered by blists - more mailing lists