Drivers' initialization routines can use __ASSERT() if they want to catch an error in a debug build.

See [Peter]

Folks, For some reason, the signature of functions passed to the DEVICE_INIT() <init_fn> parameter has a return type of 'int', but the return value is never checked within

Hello, please check this proposal and provide feedback if possible.   Background:   Currently several debugging options exists on Kconfig menu but they are not on a single debug submenu, e.g.: -

Hi Daniel, Quoting Kalowsky, Daniel (2016-02-12 12:53:49) Thanks for the background explanation. Yes, DEV_NO_SUPPORT might cover the concept however it brings another connotation which is "the

Hi Peter, Quoting Mitsis, Peter (2016-02-12 12:39:13) I guess the main reason is that the device driver APIs follows the error code format from include/device.h not the errno.h. Sure we can change

We definitely need to have one answer all drivers agree on. I had an RFC where the suspend/resume functions move to the device level and out of the device type specific APIs. This allows the

See [Peter]

Hi all, It seems we don't have a consensus about what error code the device driver should return in case a given driver API is not implemented. If we take a look at suspend() and resume() functions,