[RFC PATCH v3] drivercore: Add driver probe deferral mechanism
arnd at arndb.de
Wed Sep 28 09:04:34 EDT 2011
On Wednesday 28 September 2011, Mark Brown wrote:
> On Tue, Sep 27, 2011 at 03:08:49PM -0600, Grant Likely wrote:
> > Okay, will do. How does EPROBE_DEFER 518 sound?
> Note that I'm not sure this answers the issue I was raising - the issue
> isn't that the caller doesn't know what the error code means, the issue
> is that in some cases the driver needs to take a decision about what
> failure to get a resource means. Does it mean that the driver can work
> fine and be slightly less featureful or should it cause a deferral?
Can you think of cases where this information cannot be put into the
device tree or platform_data? If a board provides an optional feature,
I think that should be a property of the device that the driver gets,
so it can return an error when that feature is not around, or continue
when it knows that the feature will never become available.
More information about the linux-arm-kernel