Messages in this thread | | | Date | Wed, 23 Jan 2019 17:29:12 +0000 | From | Mark Brown <> | Subject | Re: [PATCH 1/1] regulator: pwm: suppress EPROBE_DEFER error message |
| |
On Wed, Jan 23, 2019 at 04:14:49PM +0000, Ben Dooks wrote: > On 2019-01-23 16:04, Mark Brown wrote:
> > This also cleans up the kernel log in the case where you've not got a > > driver enabled that you need (or it's not loading for some reason) which > > isn't super helpful when you're trying to figure out why the driver > > won't probe. There's not even anything at debug level, that would > > probably be fine.
> > The ideal thing here would be to work on setting up the dependency > > information based on DT and using that to try to sort initialization > > order so we try things in an order that minimizes the number of failed > > tries.
> Hmm, would it be useful to have a devfs file which holds the last probe > code?
You really also want the bit that says why it's deferring - "failed to get clock X" or whatever. [unhandled content-type:application/pgp-signature] | |