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
| ||
|
Message-ID: <CACRpkdZ0LTg2TFD3_gDHPnM60zkzRycXiCFsD6S760FjLmbBqg@mail.gmail.com> Date: Sat, 9 Dec 2023 22:49:19 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Vladimir Oltean <vladimir.oltean@....com> Cc: Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Andrew Lunn <andrew@...n.ch>, Luiz Angelo Daros de Luca <luizluca@...il.com>, Alvin Šipraga <alsi@...g-olufsen.dk>, Madhuri Sripada <madhuri.sripada@...rochip.com>, Marcin Wojtas <mw@...ihalf.com>, Tobias Waldekranz <tobias@...dekranz.com>, Arun Ramadoss <arun.ramadoss@...rochip.com>, "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>, Jonathan Corbet <corbet@....net> Subject: Re: [PATCH net 3/4] docs: net: dsa: update user MDIO bus documentation On Sat, Dec 9, 2023 at 2:22 AM Vladimir Oltean <vladimir.oltean@....com> wrote: > How about replacing it with this? > > Typically, the user MDIO bus accesses internal PHYs indirectly, by > reading and writing to the MDIO controller registers located in the > switch address space. Sometimes, especially if the switch is controlled > over MDIO by the host, its internal PHYs may also be accessible on the > same MDIO bus as the switch IP, but at a different MDIO address. In that > case, a direct access method for the internal PHYs is to implement the > MDIO access operations as diversions towards the parent MDIO bus of the > switch, at different MDIO addresses. > > Conceivably, the direct access method could be extended to also target > external PHYs situated on the same MDIO bus as the switch, or on a > different MDIO bus entirely, referenced through ``platform_data``. This is clear and simple to understand, go with it. Reviewed-by: Linus Walleij <linus.walleij@...aro.org> Yours, Linus Walleij
Powered by blists - more mailing lists