[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAXyoMMpf9u7aZO204moF5DHd+QR4aAxxdtEdTx-iU77DKhBDg@mail.gmail.com>
Date: Thu, 21 Aug 2025 20:50:18 +0800
From: Yangfl <mmyangfl@...il.com>
To: Andrew Lunn <andrew@...n.ch>
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 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.
Powered by blists - more mailing lists