On Wed, Mar 25, 2026 at 04:13:03PM +0100, Danilo Krummrich wrote:

On Wed Mar 25, 2026 at 5:13 AM CET, Dmitry Torokhov wrote:

quoted

That means that you are kicking the majority devices (for now) into
deferral path. I do not think this is optimal.

That's not necessary, we'd only need to kick those into the deferral path that
have PROBE_FORCE_SYNCHRONOUS, no?

Yes, it may limit the fallout, but as I explained in my other email
there seem to be a serious disconnect on what synchronous and
asynchronous probing mean.

I wonder, don't we get issues with phylib in other cases? Don't we ever
have a module resulting in creating a phy device triggering loading
another module on the same thread? Won't that result in a warning also?

Thanks.

-- 
Dmitry