Re: [PATCH v6 2/4] driver core: add deferring probe reason to devices_deferred property

On Fri, Jul 10, 2020 at 09:42:49AM +0200, Andrzej Hajda wrote:

But the provider does not know if *get is called in probe context or not, so it is not able to differentiate it.

So the whole idea is for me suspicious/wrong. Kind of proof:

1. If you insist that provider's EPROBE_ERROR must be always propagated

to driver core then.

2. You must enforce that resources can be gathered only from probe.

3. But this is against current practice, even if majority of drivers

does it from probe, there are many which doesn't.

Those drivers are probably buggy anyway at this point given probe deferral.