mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, linux@armlinux.org.uk, hkallweit1@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	thomas.petazzoni@bootlin.com
Subject: Re: [PATCH net v2 3/3] net: phy: don't try to setup PHY-driven SFP cages when using genphy
Date: Thu, 4 Jun 2026 09:28:08 +0200	[thread overview]
Message-ID: <82b0be82-5b1b-4204-8a93-a2a3d06af9c2@bootlin.com> (raw)
In-Reply-To: <20260604022729.2925198-2-kuba@kernel.org>



On 6/4/26 04:27, Jakub Kicinski wrote:
> This is an AI-generated review of your patch. The human sending this
> email has considered the AI review valid, or at least plausible.
> ---
> net: phy: don't try to setup PHY-driven SFP cages when using genphy
> 
> This change skips phy_sfp_probe() when the genphy driver is bound,
> avoiding an RTNL deadlock in sfp_bus_add_upstream() since genphy
> binding runs under RTNL while non-genphy driver binding does not.
> 
>> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
>> index a171cbe2a74a..8eace58e9f12 100644
>> --- a/drivers/net/phy/phy_device.c
>> +++ b/drivers/net/phy/phy_device.c
>> @@ -3512,9 +3512,14 @@ static int phy_setup_ports(struct phy_device *phydev)
>>  	if (ret)
>>  		return ret;
>>  
>> -	ret = phy_sfp_probe(phydev);
>> -	if (ret)
>> -		goto out;
>> +	/* We don't support SFP with genphy drivers. Also, genphy driver binding
>> +	 * occurs with RTNL help, wich will deadlock the sfp_bus_add_upstream().
>                           ^^^^
> 
> [Low]
> There is a typo in the new comment, "wich" should be "which".

Sure thing, I need to respin anyway, let me fix this :)

Maxime

> 
>> +	 */
>> +	if (!phydev->is_genphy_driven) {
>> +		ret = phy_sfp_probe(phydev);
>> +		if (ret)
>> +			goto out;
>> +	}
>>  
>>  	if (phydev->n_ports < phydev->max_n_ports) {
>>  		ret = phy_default_setup_single_port(phydev);


      reply	other threads:[~2026-06-04  7:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  8:40 [PATCH net v2 0/3] net: phy: some cleanups following phy_port SFP Maxime Chevallier
2026-06-01  8:40 ` [PATCH net v2 1/3] net: phy: clean the sfp upstream if phy probing fails Maxime Chevallier
2026-06-01  9:31   ` Nicolai Buchwitz
2026-06-05  1:24   ` Jakub Kicinski
2026-06-05  9:19     ` Maxime Chevallier
2026-06-01  8:40 ` [PATCH net v2 2/3] net: phy: remove phy ports upon probe failure Maxime Chevallier
2026-06-01  9:31   ` Nicolai Buchwitz
2026-06-04  8:02     ` Maxime Chevallier
2026-06-04  8:13       ` Nicolai Buchwitz
2026-06-04  2:27   ` Jakub Kicinski
2026-06-04  7:26     ` Maxime Chevallier
2026-06-01  8:40 ` [PATCH net v2 3/3] net: phy: don't try to setup PHY-driven SFP cages when using genphy Maxime Chevallier
2026-06-01  9:32   ` Nicolai Buchwitz
2026-06-04  2:27   ` Jakub Kicinski
2026-06-04  7:28     ` Maxime Chevallier [this message]

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=82b0be82-5b1b-4204-8a93-a2a3d06af9c2@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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