CONFIG_CAN_INIT_PRIORITY¶
CAN init priority
CAN driver init priority
Type: int
Help¶
CAN driver device initialization priority.
Help¶
CAN device driver initialization priority.
Do not mess with it unless you know what you are doing.
Note that the priority needs to be lower than the net stack
so that it can start before the networking sub-system.
Direct dependencies¶
(CAN && SHIELD_DFROBOT_CAN_BUS_V2_0) || (CAN && SHIELD_DFROBOT_CAN_BUS_V2_0) || CAN || CAN
(Includes any dependencies from ifs and menus.)
Defaults¶
80
80
80
Kconfig definitions¶
At boards/shields/dfrobot_can_bus_v2_0/Kconfig.defconfig:14
Included via Kconfig:8 → Kconfig.zephyr:20
Menu path: (Top)
config CAN_INIT_PRIORITY
int
default 80
depends on CAN && SHIELD_DFROBOT_CAN_BUS_V2_0
At boards/shields/dfrobot_can_bus_v2_0/Kconfig.defconfig:14
Included via Kconfig:8 → Kconfig.zephyr:22
Menu path: (Top)
config CAN_INIT_PRIORITY
int
default 80
depends on CAN && SHIELD_DFROBOT_CAN_BUS_V2_0
At drivers/can/Kconfig:20
Included via Kconfig:8 → Kconfig.zephyr:42 → drivers/Kconfig:82
Menu path: (Top) → Device Drivers → CAN Drivers
config CAN_INIT_PRIORITY
int "CAN init priority"
default KERNEL_INIT_PRIORITY_DEVICE
depends on CAN
help
CAN driver device initialization priority.
At drivers/can/Kconfig:63
Included via Kconfig:8 → Kconfig.zephyr:42 → drivers/Kconfig:82
Menu path: (Top) → Device Drivers → CAN Drivers
config CAN_INIT_PRIORITY
int "CAN driver init priority"
default 80
depends on CAN
help
CAN device driver initialization priority.
Do not mess with it unless you know what you are doing.
Note that the priority needs to be lower than the net stack
so that it can start before the networking sub-system.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)