From: Vladimir Oltean <olteanv@gmail.com>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: honor "max-speed" for implicit PHYs on user ports
Date: Thu, 19 Dec 2024 21:36:23 +0200 [thread overview]
Message-ID: <20241219193623.vanwiab3k7hz5tb5@skbuf> (raw)
In-Reply-To: <eb62f85a050e47c3d8d9114b33f94f97822df06b.camel@siemens.com>
On Thu, Dec 19, 2024 at 06:50:18PM +0000, Sverdlin, Alexander wrote:
> There are still switch drivers in tree, which only implement .phy_read/.phy_write
> callbacks (which means, they rely on .user_mii_bus ?), even gigabit-capable,
> such as vsc73xx, rtl8365mb, rtl8366rb... But I'm actually interested in an
> out of tree driver for a new generation of lantiq_gsw hardware, under
> Maxlinear branch, which is planned to be submitted upstream at some point.
>
> The relevant question is then, is it acceptable API (.phy_read/.phy_write),
> or any new gigabit-capable driver must use some form of mdiobus_register
> to populate the MDIO bus explicitly itself?
See the documentation patches which I never managed to finish for general
future directions:
https://patchwork.kernel.org/project/netdevbpf/patch/20231208193518.2018114-4-vladimir.oltean@nxp.com/
Not explicitly having a phy-handle should be seen a legacy feature,
which we are forced to keep for compatibility with existing drivers.
next prev parent reply other threads:[~2024-12-19 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 17:38 [PATCH net-next] net: dsa: honor "max-speed" for implicit PHYs on user ports A. Sverdlin
2024-12-19 17:46 ` Vladimir Oltean
2024-12-19 18:50 ` Sverdlin, Alexander
2024-12-19 19:36 ` Vladimir Oltean [this message]
2024-12-20 7:17 ` Sverdlin, Alexander
2024-12-20 7:30 ` Sverdlin, Alexander
2024-12-20 8:28 ` Andrew Lunn
2024-12-20 10:15 ` Vladimir Oltean
2024-12-19 17:46 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241219193623.vanwiab3k7hz5tb5@skbuf \
--to=olteanv@gmail.com \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox