Messages in this thread | | | Date | Tue, 27 Sep 2011 23:13:10 +0100 | From | Mark Brown <> | Subject | Re: [RFC PATCH v3] drivercore: Add driver probe deferral mechanism |
| |
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?
| |