netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Christian Marangi" <ansuelsmth@gmail.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Network Development" <netdev@vger.kernel.org>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Robert Marko" <robimarko@gmail.com>,
	"Daniel Golle" <daniel@makrotopia.org>
Subject: Re: Race in PHY subsystem? Attaching to PHY devices before they get probed
Date: Wed, 24 Jan 2024 19:00:27 +0000	[thread overview]
Message-ID: <ZbFeS+Jspx8T228P@shell.armlinux.org.uk> (raw)
In-Reply-To: <c3282db2-b1e5-422a-b62f-c081042da9de@lunn.ch>

On Wed, Jan 24, 2024 at 06:52:35PM +0100, Andrew Lunn wrote:
> This is assuming we cannot actually fix phylib to correctly use the
> driver model, PHYs are not visible until probe is complete, and the
> MAC drivers can handle that.

The only thing I can think is some kind of kbuild extension that looks
through all the PHY drivers that are enabled in some way, generates a
table of PHY driver match IDs, and use that as an "exclude" list for
the generic PHY drivers.

This would preclude the use of out of tree PHY drivers. Whether we
think that's a good or bad thing depends on ones own point of view.

However, the default fall-back to the generic PHY driver can't work
through the driver model because of the reasons we already know.
(If someone wants them expanded, then please ask, but Andrew and
myself are aware, so as I'm replying to Andrew here...)

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

      reply	other threads:[~2024-01-24 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  7:09 Race in PHY subsystem? Attaching to PHY devices before they get probed Rafał Miłecki
2024-01-22  9:48 ` Rafał Miłecki
2024-01-22 14:12 ` Andrew Lunn
2024-01-22 16:56   ` Russell King (Oracle)
2024-01-24 14:58     ` Christian Marangi
2024-01-24 17:52       ` Andrew Lunn
2024-01-24 19:00         ` Russell King (Oracle) [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=ZbFeS+Jspx8T228P@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=daniel@makrotopia.org \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=robimarko@gmail.com \
    --cc=zajec5@gmail.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).