drivers: can: increase default initialization priority from 50 to 80

Increase the default CAN controller driver initialization priority from KERNEL_INIT_PRIORITY_DEVICE (50) to 80 to allow CAN controllers on SPI busses have their bus initialized prior to initializing the CAN controller driver. The only in-bound dependency on CAN controller drivers - apart from application level code - is the drivers/net/canbus.c driver, which already defaults to an initialization level of 81. Fixes: zephyrproject-rtos#55745 Signed-off-by: Henrik Brix Andersen <[email protected]>
macronix · Jun 1, 2023 · b12eb78 · b12eb78
1 parent b716027
commit b12eb78
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 14 deletions.
diff --git a/boards/shields/mcp2515/Kconfig.defconfig b/boards/shields/mcp2515/Kconfig.defconfig
diff --git a/drivers/can/Kconfig b/drivers/can/Kconfig
@@ -19,7 +19,7 @@ source "subsys/logging/Kconfig.template.log_config"
 
 config CAN_INIT_PRIORITY
 	int "CAN driver init priority"
-	default KERNEL_INIT_PRIORITY_DEVICE
+	default 80
 	help
 	  CAN driver device initialization priority.