From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: probe PHY drivers synchronously
Date: Fri, 27 Mar 2020 00:34:11 +0100 [thread overview]
Message-ID: <20200326233411.GG3819@lunn.ch> (raw)
In-Reply-To: <86582ac9-e600-bdb5-3d2e-d2d99ed544f4@gmail.com>
On Thu, Mar 26, 2020 at 07:16:23PM +0100, Heiner Kallweit wrote:
> If we have scenarios like
>
> mdiobus_register()
> -> loads PHY driver module(s)
> -> registers PHY driver(s)
> -> may schedule async probe
> phydev = mdiobus_get_phy()
> <phydev action involving PHY driver>
>
> or
>
> phydev = phy_device_create()
> -> loads PHY driver module
> -> registers PHY driver
> -> may schedule async probe
> <phydev action involving PHY driver>
>
> then we expect the PHY driver to be bound to the phydev when triggering
> the action. This may not be the case in case of asynchronous probing.
> Therefore ensure that PHY drivers are probed synchronously.
Hi Heiner
We have been doing asynchronous driver loads since forever, and not
noticed any problem. Do you have a real example of it going wrong?
Andrew
next prev parent reply other threads:[~2020-03-26 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 18:16 [PATCH net-next] net: phy: probe PHY drivers synchronously Heiner Kallweit
2020-03-26 23:34 ` Andrew Lunn [this message]
2020-03-26 23:42 ` Heiner Kallweit
2020-03-26 23:44 ` Andrew Lunn
2020-03-26 23:57 ` Heiner Kallweit
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=20200326233411.GG3819@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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.