On Thu, 2016-02-18 at 12:34 -0800, Dirk Brandewie wrote:
How about a CONFIG option to determine if kernel should abort boot? The
behavior should be determined by the kind of application. Some can live
with less features while for others it is all or nothing. In both cases
a logging feature that can be queried by the app would be useful.
+1 _sys_device_do_config_level() should at least pass on the errorAny of those could be a valid approach I think, but we have to decide on
returned even if one device fails. This as well as the
"resume_all/suspend_all" functions can be called by app in power
management case. It would be useful for the app to know that something
Question still remains whether _sys_device_do_config_level() should
continue with other devices if one fails. IMO it should continue but
should return error if one device had failed. At boot time, kernel can
save the error condition somewhere to be queried by the app.
The app would be anyway getting a failure when it tries to use theBrainstorming:
device. It most probably cannot rectify any device error on the fly with
more detailed info. Just my thought
A simple status from _sys_device_do_config_level() is probably enough so
the app can decide whether to continue or abort.