Re: [PATCH net-next RFC v2 0/6] net: phy: Introduce a port representation

[Kory Maincent <kory.maincent@bootlin.com>]

On Thu, 23 Jan 2025 11:31:21 +0100
Kory Maincent <kory.maincent@bootlin.com> wrote:

> On Wed, 22 Jan 2025 18:42:45 +0100
> Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
> 
> > Hello everyone,
> > 
> > This is a second RFC for the introduction of a front-facing interfaces
> > for ethernet devices.
> > 
> > The firts RFC[1] already got some reviews, focusing on the DT part of
> > that work. To better lay the ground for further discussions, this second
> > round includes a binding :)
> > 
> > Oleksij suggested some further possibilities for improving this binding,
> > as we could consider describing connectors in great details for
> > crossover detection, PoE ping mappings, etc. However, as this is
> > preliminary work, the included binding is still quite simple but can
> > certainly be extended.
> > 
> > This RFC V2 doesn't bring much compared to V1 :
> >  - A binding was introduced
> >  - A warning has been fixed in the dp83822 patch
> >  - The "lanes" property has been made optional  
> 
> Small question, I know you want to begin with something simple but would it be
> possible to consider how to support the port representation in NIT and
> switch drivers? Maybe it is out of your scope but it would be nice if you
> consider how NIT and switches can support it in your development.

s/NIT/NIC/

Sorry.
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com