On 2019-08-08 14:44, Mark Brown wrote:
On Thu, Aug 08, 2019 at 02:36:55PM +0200, Stefan Agner wrote:
From: Stefan Agner stefan.agner@toradex.com
Deferred probes shouldn't cause error messages in the boot log. Avoid printing with dev_err() in case EPROBE_DEFER is the return value.
No, they absolutely should tell the user why they are deferring so the user has some information to go on when they're trying to figure out why their device isn't instantiating.
Hm, I see, if the driver defers and does not manage in the end, then the messages are indeed helpful.
But can we lower severity, e.g. to dev_info? In my case it succeeds in the end, just defers about 6 times. I have 3 links which then leads to 18 error messages which confuse users... From what I can see soc_init_dai_link() would print dev_err in case there is an actual error.
-- Stefan