Messages in this thread | | | Date | Thu, 2 Sep 2021 12:37:34 +0200 | From | Greg Kroah-Hartman <> | Subject | Re: [RFC PATCH net-next 1/3] net: phy: don't bind genphy in phy_attach_direct if the specific driver defers probe |
| |
On Thu, Sep 02, 2021 at 01:11:50PM +0300, Vladimir Oltean wrote: > On Thu, Sep 02, 2021 at 07:43:10AM +0200, Greg Kroah-Hartman wrote: > > Wait, no, this should not be a "special" thing, and why would the list > > of deferred probe show this? > > Why as in why would it work/do what I want, or as in why would you want to do that?
Both! :)
> > If a bus wants to have this type of "generic vs. specific" logic, then > > it needs to handle it in the bus logic itself as that does NOT fit into > > the normal driver model at all. Don't try to get a "hint" of this by > > messing with the probe function list. > > Where and how? Do you have an example?
No I do not, sorry, most busses do not do this for obvious ordering / loading / we are not that crazy reasons.
What is causing this all to suddenly break? The devlink stuff?
thanks,
greg k-h
| |