[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <367d2734-13bb-44f9-832c-f17b1a2194e2@lunn.ch>
Date: Sun, 15 Oct 2023 00:15:48 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Gregory Clement <gregory.clement@...tlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Russell King <linux@...linux.org.uk>,
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>,
Christian Marangi <ansuelsmth@...il.com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/5] dt-bindings: marvell: Rewrite MV88E6xxx
in schema
> + mdio:
> + $ref: /schemas/net/mdio.yaml#
> + unevaluatedProperties: false
> + description: Marvell MV88E6xxx switches have an internal mdio bus to
> + access switch ports, which is handled in this node.
This is not quite correct. For marvell,mv88e6085 and marvell,mv88e6250
there is one MDIO bus, which can be used both internally and
externally.
For marvell,mv88e6190, there are two MDIO buses. This one is used only
internally, and 'mdio-external' is connected to pins for external use.
Also, its not used to access switch ports. It is used to access PHYs
which can connected to switch ports.
Andrew
Powered by blists - more mailing lists