From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Fedrau Dimitri (LED)" <Dimitri.Fedrau@liebherr.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"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"
<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>,
"Marek Behún" <kabel@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Simon Horman" <horms@kernel.org>,
"mwojtas@chromium.org" <mwojtas@chromium.org>,
"Antoine Tenart" <atenart@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Sean Anderson" <seanga2@gmail.com>,
"dima.fedrau@gmail.com" <dima.fedrau@gmail.com>
Subject: Re: [PATCH net-next v4 04/15] net: phy: dp83822: Add support for phy_port representation
Date: Mon, 17 Feb 2025 10:26:03 +0100 [thread overview]
Message-ID: <20250217102603.3e9f79c6@fedora.home> (raw)
In-Reply-To: <DB8P192MB08386B9F0FB342EB7B0FA785F3F92@DB8P192MB0838.EURP192.PROD.OUTLOOK.COM>
Hello Dimitri,
On Sat, 15 Feb 2025 11:31:28 +0000
"Fedrau Dimitri (LED)" <Dimitri.Fedrau@liebherr.com> wrote:
> Hi Maxime,
>
> > -----Ursprüngliche Nachricht-----
> > Von: Maxime Chevallier <maxime.chevallier@bootlin.com>
> > Gesendet: Donnerstag, 13. Februar 2025 11:16
> >
> [...]
> >
> > @@ -781,17 +782,6 @@ static int dp83822_of_init(struct phy_device *phydev)
> > struct device *dev = &phydev->mdio.dev;
> > const char *of_val;
> >
> > - /* Signal detection for the PHY is only enabled if the FX_EN and the
> > - * SD_EN pins are strapped. Signal detection can only enabled if FX_EN
> > - * is strapped otherwise signal detection is disabled for the PHY.
> > - */
> Does it make sense to keep the comment ?
>
I think so, this behaviour isn't expected to change with this patchset
> > - if (dp83822->fx_enabled && dp83822->fx_sd_enable)
> > - dp83822->fx_signal_det_low = device_property_present(dev,
> > - "ti,link-loss-low");
> > - if (!dp83822->fx_enabled)
> > - dp83822->fx_enabled = device_property_present(dev,
> > - "ti,fiber-mode");
> > -
> > if (!device_property_read_string(dev, "ti,gpio2-clk-out", &of_val)) {
> > if (strcmp(of_val, "mac-if") == 0) {
> > dp83822->gpio2_clk_out = DP83822_CLK_SRC_MAC_IF;
> > @@ -884,6 +874,43 @@ static int dp83822_read_straps(struct phy_device *phydev)
> > return 0;
> > }
> >
> > +static int dp83822_attach_port(struct phy_device *phydev, struct phy_port *port)
> > +{
> > + struct dp83822_private *dp83822 = phydev->priv;
> > + int ret;
> > +
> > + if (port->mediums) {
> > + if (phy_port_is_fiber(port) ||
> > + port->mediums & BIT(ETHTOOL_LINK_MEDIUM_BASEX))
> > + dp83822->fx_enabled = true;
> > + } else {
> > + ret = dp83822_read_straps(phydev);
> > + if (ret)
> > + return ret;
> > +
> > +#ifdef CONFIG_OF_MDIO
> > + if (dp83822->fx_enabled && dp83822->fx_sd_enable)
> > + dp83822->fx_signal_det_low =
> > + device_property_present(dev, "ti,link-loss-low");
> > + if (!dp83822->fx_enabled)
> > + dp83822->fx_enabled =
> > + device_property_present(dev, "ti,fiber-mode");
> > +#endif
>
> I think this is to make it backwards compatible to the dp83822 bindings,
> is it worth mentioning this in a comment ?
Good point yes, I'll mention that.
> > +
> > + if (dp83822->fx_enabled) {
> > + port->lanes = 1;
> > + port->mediums = BIT(ETHTOOL_LINK_MEDIUM_BASEF) |
> > + BIT(ETHTOOL_LINK_MEDIUM_BASEX);
> > + } else {
> > + /* This PHY can only to 100BaseTX max, so on 2 lanes */
> > + port->lanes = 2;
> > + port->mediums = BIT(ETHTOOL_LINK_MEDIUM_BASET);
> > + }
> > + }
> > +
> > + return 0;
> > +}
> > +
> > static int dp8382x_probe(struct phy_device *phydev)
> > {
> > struct dp83822_private *dp83822;
> > @@ -900,25 +927,13 @@ static int dp8382x_probe(struct phy_device *phydev)
> >
> > static int dp83822_probe(struct phy_device *phydev)
> > {
> > - struct dp83822_private *dp83822;
> > int ret;
> >
> > ret = dp8382x_probe(phydev);
> > if (ret)
> > return ret;
> >
> > - dp83822 = phydev->priv;
> > -
> > - ret = dp83822_read_straps(phydev);
> > - if (ret)
> > - return ret;
> > -
> > - ret = dp83822_of_init(phydev);
> > - if (ret)
> > - return ret;
> > -
> > - if (dp83822->fx_enabled)
> > - phydev->port = PORT_FIBRE;
> > + dp83822_of_init(phydev);
>
> Keep the check of the return value.
Ah yes indeed, the check should indeed stay. Thanks !
> >
> > return 0;
> > }
> > @@ -1104,6 +1119,7 @@ static int dp83822_led_hw_control_get(struct phy_device *phydev, u8 index,
> > .led_hw_is_supported = dp83822_led_hw_is_supported, \
> > .led_hw_control_set = dp83822_led_hw_control_set, \
> > .led_hw_control_get = dp83822_led_hw_control_get, \
> > + .attach_port = dp83822_attach_port \
> > }
> >
> > #define DP83825_PHY_DRIVER(_id, _name) \
> > --
> > 2.48.1
>
> Best regards,
> Dimitri Fedrau
Thanks for reviewing,
Maxime
next prev parent reply other threads:[~2025-02-17 9:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 10:15 [PATCH net-next v4 00/15] Introduce an ethernet port representation Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 01/15] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 02/15] net: ethtool: Export the link_mode_params definitions Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 03/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 04/15] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-02-15 11:31 ` AW: " Fedrau Dimitri (LED)
2025-02-17 9:26 ` Maxime Chevallier [this message]
2025-02-13 10:15 ` [PATCH net-next v4 05/15] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-02-15 18:57 ` Russell King (Oracle)
2025-02-17 8:29 ` Maxime Chevallier
2025-02-17 13:43 ` Andrew Lunn
2025-02-17 14:22 ` Maxime Chevallier
2025-02-17 15:29 ` Andrew Lunn
2025-02-17 14:21 ` Russell King (Oracle)
2025-02-17 14:49 ` Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 06/15] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 07/15] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 08/15] net: phy: marvell: " Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 09/15] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 10/15] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-02-13 10:15 ` [PATCH net-next v4 11/15] net: phy: qca807x: " Maxime Chevallier
2025-02-13 10:16 ` [PATCH net-next v4 12/15] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-02-13 10:16 ` [PATCH net-next v4 13/15] net: phy: dp83822: Add SFP support through the phy_port interface Maxime Chevallier
2025-02-13 10:16 ` [PATCH net-next v4 14/15] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
2025-02-13 10:16 ` [PATCH net-next v4 15/15] dt-bindings: net: Introduce the phy-port description Maxime Chevallier
2025-02-19 22:35 ` Rob Herring
2025-02-20 8:35 ` Maxime Chevallier
2025-02-15 0:53 ` [PATCH net-next v4 00/15] Introduce an ethernet port representation Jakub Kicinski
2025-02-17 9:20 ` Maxime Chevallier
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=20250217102603.3e9f79c6@fedora.home \
--to=maxime.chevallier@bootlin.com \
--cc=Dimitri.Fedrau@liebherr.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--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=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=seanga2@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: 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).