[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164945401246.15686.1891424640500147918.git-patchwork-notify@kernel.org>
Date: Fri, 08 Apr 2022 21:40:12 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, kuba@...nel.org,
davem@...emloft.net, andrew@...n.ch, hkallweit1@...il.com,
linux@...linux.org.uk, f.fainelli@...il.com,
geert+renesas@...der.be, saravanak@...gle.com, robh@...nel.org,
gregkh@...uxfoundation.org, rafael@...nel.org, robin.murphy@....com
Subject: Re: [PATCH v2 net] net: mdio: don't defer probe forever if PHY IRQ
provider is missing
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 7 Apr 2022 19:55:38 +0300 you wrote:
> When a driver for an interrupt controller is missing, of_irq_get()
> returns -EPROBE_DEFER ad infinitum, causing
> fwnode_mdiobus_phy_device_register(), and ultimately, the entire
> of_mdiobus_register() call, to fail. In turn, any phy_connect() call
> towards a PHY on this MDIO bus will also fail.
>
> This is not what is expected to happen, because the PHY library falls
> back to poll mode when of_irq_get() returns a hard error code, and the
> MDIO bus, PHY and attached Ethernet controller work fine, albeit
> suboptimally, when the PHY library polls for link status. However,
> -EPROBE_DEFER has special handling given the assumption that at some
> point probe deferral will stop, and the driver for the supplier will
> kick in and create the IRQ domain.
>
> [...]
Here is the summary with links:
- [v2,net] net: mdio: don't defer probe forever if PHY IRQ provider is missing
https://git.kernel.org/netdev/net/c/74befa447e68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists