8 Aug
2019
8 Aug
'19
3 p.m.
On Thu, 08 Aug 2019 14:44:37 +0200, 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.
But it's no real error that *must* be printed on the console, either. Maybe downgrading the printk level?
thanks,
Takashi