Thread (1 message) flat view 1 message, 1 author, 2020-06-24

Re: [RESEND PATCH v5 4/5] drm/bridge/sii8620: fix resource acquisition error handling

From: Mark Brown <broonie@kernel.org>
Date: 2020-06-24 14:11:44
Also in: dri-devel, lkml

On Wed, Jun 24, 2020 at 03:43:10PM +0200, Andrzej Hajda wrote:
On 24.06.2020 15:25, Mark Brown wrote:
quoted
If we silently ignore all deferred probe errors we make it hard for
anyone who is experiencing issues with deferred probe to figure out what
they're missing.  We should at least be logging problems at debug level
so there's something for people to go on without having to hack the
kernel source.
But you can always do:
cat /sys/kernel/debug/devices_deferred
And you will find there deferred probe reason (thanks to patch 2/5).
Right, my point is more that we shouldn't be promoting discarding the
diagnostics entirely but rather saying that we want to redirect those
somewhere else.
Eventually if you want it in dmesg anyway, one can adjust probe_err function
to log probe error on debug level as well.
That would most likely be very useful as a boot option for problems that
occur before we get a console up.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help