All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH net] net: mdio: don't defer probe forever if PHY IRQ provider is missing
Date: Wed, 6 Apr 2022 15:34:43 -0700	[thread overview]
Message-ID: <20220406153443.51ad52f8@kernel.org> (raw)
In-Reply-To: <20220406202323.3390405-1-vladimir.oltean@nxp.com>

On Wed,  6 Apr 2022 23:23:23 +0300 Vladimir Oltean wrote:
> diff --git a/drivers/net/mdio/fwnode_mdio.c b/drivers/net/mdio/fwnode_mdio.c
> index 1becb1a731f6..1c1584fca632 100644
> --- a/drivers/net/mdio/fwnode_mdio.c
> +++ b/drivers/net/mdio/fwnode_mdio.c
> @@ -43,6 +43,11 @@ int fwnode_mdiobus_phy_device_register(struct mii_bus *mdio,
>  	int rc;
>  
>  	rc = fwnode_irq_get(child, 0);
> +	/* Don't wait forever if the IRQ provider doesn't become available,
> +	 * just fall back to poll mode
> +	 */
> +	if (rc == -EPROBE_DEFER)
> +		rc = driver_deferred_probe_check_state(&phy->mdio.dev);

This one's not exported, allmodconfig build fails.

  reply	other threads:[~2022-04-06 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:23 [PATCH net] net: mdio: don't defer probe forever if PHY IRQ provider is missing Vladimir Oltean
2022-04-06 22:34 ` Jakub Kicinski [this message]
2022-04-06 23:19   ` Vladimir Oltean
2022-04-07  0:25     ` Jakub Kicinski
2022-04-07  5:23       ` Greg Kroah-Hartman
2022-04-07  5:35         ` Jakub Kicinski
2022-04-07 17:04           ` Greg Kroah-Hartman

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=20220406153443.51ad52f8@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=hkallweit1@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robin.murphy@arm.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 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.