From: Andrew Lunn <andrew@lunn.ch> To: Maxime Chevallier <maxime.chevallier@bootlin.com> Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com, "Jakub Kicinski" <kuba@kernel.org>, "Eric Dumazet" <edumazet@google.com>, "Paolo Abeni" <pabeni@redhat.com>, "Russell King" <linux@armlinux.org.uk>, 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>, "Köry Maincent" <kory.maincent@bootlin.com>, "Jesse Brandeburg" <jesse.brandeburg@intel.com>, "Jonathan Corbet" <corbet@lwn.net>, "Marek Behún" <kabel@kernel.org>, "Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>, "Oleksij Rempel" <o.rempel@pengutronix.de>, "Nicolò Veronese" <nicveronese@gmail.com> Subject: Re: [PATCH net-next v4 13/13] Documentation: networking: document phy_link_topology Date: Mon, 18 Dec 2023 11:10:29 +0100 [thread overview] Message-ID: <32461e61-b518-4ecc-bf51-7d22f8580212@lunn.ch> (raw) In-Reply-To: <20231215171237.1152563-14-maxime.chevallier@bootlin.com> > +An Ethernet Interface from userspace's poing of view is nothing but a point > +:c:type:`struct net_device <net_device>`, which exposes configuration options > +trough the legacy ioctls and the ethool netlink commands. The base assumption through > +when designing these configuration channels were that the link looked > +something like this :: > + > + +-----------------------+ +----------+ +--------------+ > + | Ethernet Controller / | | Ethernet | | Connector / | > + | MAC | ------ | PHY | ---- | Port | ---... to LP > + +-----------------------+ +----------+ +--------------+ > + struct net_device struct phy_device > + > +Commands that needs to configure the PHY will go through the net_device.phydev > +field to reach the PHY and perform the relevant configuration. > + > +This assumption falls appart in more complex topologies that can arise when, apart. Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch> To: Maxime Chevallier <maxime.chevallier@bootlin.com> Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com, "Jakub Kicinski" <kuba@kernel.org>, "Eric Dumazet" <edumazet@google.com>, "Paolo Abeni" <pabeni@redhat.com>, "Russell King" <linux@armlinux.org.uk>, 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>, "Köry Maincent" <kory.maincent@bootlin.com>, "Jesse Brandeburg" <jesse.brandeburg@intel.com>, "Jonathan Corbet" <corbet@lwn.net>, "Marek Behún" <kabel@kernel.org>, "Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>, "Oleksij Rempel" <o.rempel@pengutronix.de>, "Nicolò Veronese" <nicveronese@gmail.com> Subject: Re: [PATCH net-next v4 13/13] Documentation: networking: document phy_link_topology Date: Mon, 18 Dec 2023 11:10:29 +0100 [thread overview] Message-ID: <32461e61-b518-4ecc-bf51-7d22f8580212@lunn.ch> (raw) In-Reply-To: <20231215171237.1152563-14-maxime.chevallier@bootlin.com> > +An Ethernet Interface from userspace's poing of view is nothing but a point > +:c:type:`struct net_device <net_device>`, which exposes configuration options > +trough the legacy ioctls and the ethool netlink commands. The base assumption through > +when designing these configuration channels were that the link looked > +something like this :: > + > + +-----------------------+ +----------+ +--------------+ > + | Ethernet Controller / | | Ethernet | | Connector / | > + | MAC | ------ | PHY | ---- | Port | ---... to LP > + +-----------------------+ +----------+ +--------------+ > + struct net_device struct phy_device > + > +Commands that needs to configure the PHY will go through the net_device.phydev > +field to reach the PHY and perform the relevant configuration. > + > +This assumption falls appart in more complex topologies that can arise when, apart. Andrew _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-18 10:10 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-15 17:12 [PATCH net-next v4 00/13] Introduce PHY listing and link_topology tracking Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-15 17:12 ` [PATCH net-next v4 01/13] net: phy: Introduce ethernet link topology representation Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-15 21:45 ` Vladimir Oltean 2023-12-15 21:45 ` Vladimir Oltean 2023-12-17 16:57 ` Andrew Lunn 2023-12-17 16:57 ` Andrew Lunn 2023-12-18 8:49 ` Maxime Chevallier 2023-12-18 8:49 ` Maxime Chevallier 2023-12-18 9:11 ` Maxime Chevallier 2023-12-18 9:11 ` Maxime Chevallier 2023-12-18 6:04 ` kernel test robot 2023-12-18 6:04 ` kernel test robot 2023-12-18 8:10 ` kernel test robot 2023-12-18 8:10 ` kernel test robot 2023-12-15 17:12 ` [PATCH net-next v4 02/13] net: sfp: pass the phy_device when disconnecting an sfp module's PHY Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-15 17:12 ` [PATCH net-next v4 03/13] net: phy: add helpers to handle sfp phy connect/disconnect Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-15 17:12 ` [PATCH net-next v4 04/13] net: sfp: Add helper to return the SFP bus name Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-17 17:07 ` Andrew Lunn 2023-12-17 17:07 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 05/13] net: ethtool: Allow passing a phy index for some commands Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-16 11:48 ` kernel test robot 2023-12-16 11:48 ` kernel test robot 2023-12-17 17:11 ` Andrew Lunn 2023-12-17 17:11 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 06/13] netlink: specs: add phy-index as a header parameter Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-17 17:11 ` Andrew Lunn 2023-12-17 17:11 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 07/13] net: ethtool: Introduce a command to list PHYs on an interface Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-19 8:55 ` Simon Horman 2023-12-19 8:55 ` Simon Horman 2023-12-15 17:12 ` [PATCH net-next v4 08/13] netlink: specs: add ethnl PHY_GET command set Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-15 17:12 ` [PATCH net-next v4 09/13] net: ethtool: plca: Target the command to the requested PHY Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-18 9:55 ` Andrew Lunn 2023-12-18 9:55 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 10/13] net: ethtool: pse-pd: " Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-18 9:58 ` Andrew Lunn 2023-12-18 9:58 ` Andrew Lunn 2023-12-21 17:31 ` Maxime Chevallier 2023-12-21 17:31 ` Maxime Chevallier 2023-12-15 17:12 ` [PATCH net-next v4 11/13] net: ethtool: cable-test: " Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-18 9:58 ` Andrew Lunn 2023-12-18 9:58 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 12/13] net: ethtool: strset: Allow querying phy stats by index Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-18 10:00 ` Andrew Lunn 2023-12-18 10:00 ` Andrew Lunn 2023-12-15 17:12 ` [PATCH net-next v4 13/13] Documentation: networking: document phy_link_topology Maxime Chevallier 2023-12-15 17:12 ` Maxime Chevallier 2023-12-18 10:10 ` Andrew Lunn [this message] 2023-12-18 10:10 ` Andrew Lunn 2023-12-19 8:58 ` Simon Horman 2023-12-19 8:58 ` Simon Horman
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=32461e61-b518-4ecc-bf51-7d22f8580212@lunn.ch \ --to=andrew@lunn.ch \ --cc=christophe.leroy@csgroup.eu \ --cc=corbet@lwn.net \ --cc=davem@davemloft.net \ --cc=edumazet@google.com \ --cc=f.fainelli@gmail.com \ --cc=herve.codina@bootlin.com \ --cc=hkallweit1@gmail.com \ --cc=jesse.brandeburg@intel.com \ --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=netdev@vger.kernel.org \ --cc=nicveronese@gmail.com \ --cc=o.rempel@pengutronix.de \ --cc=pabeni@redhat.com \ --cc=piergiorgio.beruto@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.