drivers: can: Refactor drivers to use shared init priority
Refactors all of the CAN drivers to use a shared driver class initialization priority configuration, CONFIG_CAN_INIT_PRIORITY, to allow configuring CAN drivers separately from other devices. This is similar to other driver classes like I2C and SPI. The default is set to CONFIG_KERNEL_INIT_PRIORITY_DEVICE to preserve the existing default initialization priority for most drivers. The exception is the mcp2515 driver which has a dependency on a SPI driver and must therefore initialize later than the default device priority. Signed-off-by: Maureen Helm <maureen.helm@intel.com>
This commit is contained in:
parent
27907d0625
commit
e297f8ee26
9 changed files with 21 additions and 19 deletions
|
@ -279,7 +279,7 @@ static struct can_stm32fd_data can_stm32fd_dev_data_##inst;
|
|||
#define CAN_STM32FD_DEVICE_INST(inst) \
|
||||
DEVICE_DT_INST_DEFINE(inst, &can_stm32fd_init, NULL, \
|
||||
&can_stm32fd_dev_data_##inst, &can_stm32fd_cfg_##inst, \
|
||||
POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEVICE, \
|
||||
POST_KERNEL, CONFIG_CAN_INIT_PRIORITY, \
|
||||
&can_api_funcs);
|
||||
|
||||
#define CAN_STM32FD_INST(inst) \
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue