mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-15 18:51:57 +00:00
If this call receives an invalid device pointer as argument it assumes that the `device` is not ready for usage. This routine is currently called by two device specific APIs: - device_usable_check(const struct device *dev) - device_is_ready(const struct device *dev) The device-specific APIs documentation claims that these two routines must be called with a device pointer captured from DEVICE_DT_GET(). So passing NULL is a violation of the rule. Nevertheless, is quite common in drivers to assign NULL to a device pointer if the corresponding DT property has not been found (e.g. a not used gpio interrupt declaration for a given device instance) and seems legit to interpret this condition same as the device is not ready for usage. Signed-off-by: Armando Visconti <armando.visconti@st.com> |
||
---|---|---|
.. | ||
include | ||
paging | ||
atomic_c.c | ||
banner.c | ||
cache_handlers.c | ||
CMakeLists.txt | ||
compiler_stack_protect.c | ||
condvar.c | ||
device.c | ||
errno.c | ||
fatal.c | ||
futex.c | ||
idle.c | ||
init.c | ||
Kconfig | ||
kheap.c | ||
mailbox.c | ||
mem_domain.c | ||
mem_slab.c | ||
mempool.c | ||
mmu.c | ||
msg_q.c | ||
mutex.c | ||
pipes.c | ||
poll.c | ||
queue.c | ||
sched.c | ||
sem.c | ||
smp.c | ||
stack.c | ||
system_work_q.c | ||
thread.c | ||
timeout.c | ||
timer.c | ||
userspace_handler.c | ||
userspace.c | ||
version.c | ||
work.c | ||
xip.c |