U-Boot PHY_MSCC vs PHY_VITESSE

[Tom Rini]

On Tue, Sep 30, 2025 at 02:49:38PM +0800, Peng Fan wrote:
> Hi Tom,
> 
> On Mon, Sep 29, 2025 at 04:43:36PM -0600, Tom Rini wrote:
> >Hey all,
> >
> >As part of working on "allyesconfig" support I ran into the following
> >problem. Both drivers/net/phy/mscc.c and drivers/net/phy/vitesse.c
> >implement support for the VSC8584 PHY. The vitesse.c driver is much
> >older and only had VSC8584 support added for a specific Freescale
> >Layerscape platform whereas mscc.c is modern and been updated with
> >newer PHYs as well. And we need one driver to support this phy, not two.
> >I am inclined to remove support from vitesse.c. However, only 4
> >platforms use the PHY_MSCC driver and everyone else uses PHY_VITESSE.
> >
> >I'm cc'ing all of the board maintainers (other than PowerPC platforms)
> >that use PHY_VITESEE today to see what their feedback is on which way to
> >go here. I'm ignoring PowerPC because that can just stay on the
> >PHY_VITESSE driver based on timing of changes in git log.
> 
> There are many Layerscape boards that we need to support are still using
> PHY_VITESEE. I need to check internal to ask for resources to help on
> the migration.  BTW, to support allyesconfig, is it feasible to
> make the two configs exclusive, saying "depends on !X".

There are Kconfig workarounds available, but there's enough work to be
done still that I'd rather see about fixing the root causes, or as a
worst case here, remove the duplicate code from PHY_VITESSE and enable
PHY_MSCC as well on the boards that need something from each driver
still, if we can't switch them to the newer driver outright.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20250930/bf171bc2/attachment.sig>