From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, f.fainelli@gmail.com,
geert+renesas@glider.be, saravanak@google.com, robh@kernel.org,
gregkh@linuxfoundation.org, rafael@kernel.org,
robin.murphy@arm.com
Subject: Re: [PATCH v2 net] net: mdio: don't defer probe forever if PHY IRQ provider is missing
Date: Fri, 08 Apr 2022 21:40:12 +0000 [thread overview]
Message-ID: <164945401246.15686.1891424640500147918.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407165538.4084809-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2022-04-08 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 16:55 [PATCH v2 net] net: mdio: don't defer probe forever if PHY IRQ provider is missing Vladimir Oltean
2022-04-07 17:04 ` Greg Kroah-Hartman
2022-04-07 17:57 ` Florian Fainelli
2022-04-08 21:40 ` patchwork-bot+netdevbpf [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=164945401246.15686.1891424640500147918.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.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).