netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	"Marek Behún" <kabel@kernel.org>,
	"Nicolò Veronese" <nicveronese@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	mwojtas@chromium.org, "Antoine Tenart" <atenart@kernel.org>
Subject: Re: [PATCH net-next RFC 0/5] net: phy: Introduce a port representation
Date: Tue, 7 Jan 2025 15:53:57 +0100	[thread overview]
Message-ID: <Z31ABd8pdBjJtTiE@pengutronix.de> (raw)
In-Reply-To: <20250107154302.628e7982@kmaincent-XPS-13-7390>

On Tue, Jan 07, 2025 at 03:43:02PM +0100, Kory Maincent wrote:
> On Tue, 7 Jan 2025 15:02:46 +0100
> Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> 
> > On Tue, Jan 07, 2025 at 02:26:05PM +0100, Kory Maincent wrote:
> > > On Thu, 2 Jan 2025 18:03:52 +0100
> > > Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> > >   
> > > > On Thu, Jan 02, 2025 at 10:48:05AM +0000, Russell King (Oracle) wrote:  
> >  [...]  
> >  [...]  
> > > 
> > > Couldn't we begin with something simple like the following and add all the
> > > transformers and pairs information as you described later if the community
> > > feels we need it?
> > > 
> > > mdis {
> > > 
> > >     /* 1000BaseT Port with Ethernet and PoE */
> > >     mdi0: ethernet-mdi@0 {
> > >         reg = <0>; /* Port index */
> > >         label = "ETH0"; /* Physical label on the device */
> > >         connector = "RJ45"; /* Connector type */
> > >         supported-modes = <10BaseT 100BaseTX 1000BaseT>; /* Supported modes
> > > */ lanes = <2>;
> > >         variant = "MDI-X"; /* MDI or MDI-X */
> > >         pse = <&pse1>;
> > >     };
> > > };  
> > This was only the pair swap. How to reflect the polarity swap withing
> > the pairs?
> 
> Indeed I see what you mean. Maybe we could add it later as optional binding and
> only focus for now on the current needs.
> According to Maxime proposition he wants the connector types and the
> supported modes (or number of lanes). On my side I am interested in the PSE
> phandle.
> 
> We could begin with this:
> mdis {
>     /* 1000BaseT Port with Ethernet and PoE */
>     mdi0: ethernet-mdi@0 {
>         reg = <0>; /* Port index */
>         label = "ETH0"; /* Physical label on the device */
>         connector = "RJ45"; /* Connector type */
>         supported-modes = <10BaseT 100BaseTX 1000BaseT>; /* Supported modes */
>         pse = <&pse1>;
>     };
> };  
> 
> Your proposition will stay in our mind for future development on the subject.

Perfect :)

> I think we currently don't have enough time available to develop the full
> package.

Yes, no one do.

> What do you think?

Sounds good!

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2025-01-07 14:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 20:14 [PATCH net-next RFC 0/5] net: phy: Introduce a port representation Maxime Chevallier
2024-12-20 20:15 ` [PATCH net-next RFC 1/5] net: ethtool: common: Make BaseT a 4-lanes mode Maxime Chevallier
2024-12-20 20:15 ` [PATCH net-next RFC 2/5] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2024-12-20 20:15 ` [PATCH net-next RFC 3/5] net: ethtool: Export the link_mode_params definitions Maxime Chevallier
2024-12-20 20:15 ` [PATCH net-next RFC 4/5] net: phy: Introduce PHY ports representation Maxime Chevallier
2024-12-20 20:15 ` [PATCH net-next RFC 5/5] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2024-12-22 15:59 ` [PATCH net-next RFC 0/5] net: phy: Introduce a port representation Oleksij Rempel
2024-12-22 18:54   ` Oleksij Rempel
2025-01-02 10:48     ` Russell King (Oracle)
2025-01-02 17:03       ` Oleksij Rempel
2025-01-07 13:26         ` Kory Maincent
2025-01-07 14:02           ` Oleksij Rempel
2025-01-07 14:43             ` Kory Maincent
2025-01-07 14:53               ` Oleksij Rempel [this message]
2025-01-07 15:14             ` Russell King (Oracle)
2025-01-07 15:54               ` Oleksij Rempel
2025-01-07 15:12           ` Russell King (Oracle)
2025-01-07 16:13             ` Andrew Lunn
2025-01-07 16:15             ` Maxime Chevallier
2025-01-07 16:22               ` Andrew Lunn
2025-01-07 16:41                 ` Oleksij Rempel
2025-01-07 16:49                   ` Oleksij Rempel
2025-01-08  7:25                   ` Maxime Chevallier
2025-01-08  8:12                     ` Oleksij Rempel
2025-01-04 22:23     ` Kory Maincent
2025-01-06 18:17       ` Oleksij Rempel

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=Z31ABd8pdBjJtTiE@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=atenart@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=herve.codina@bootlin.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kabel@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mwojtas@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicveronese@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vladimir.oltean@nxp.com \
    /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;
as well as URLs for NNTP newsgroup(s).