From b12eb78f35cecfda1e80cb37564d97b8a424f53b Mon Sep 17 00:00:00 2001 From: Henrik Brix Andersen Date: Thu, 1 Jun 2023 18:21:04 +0200 Subject: [PATCH] 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: #55745 Signed-off-by: Henrik Brix Andersen --- boards/shields/mcp2515/Kconfig.defconfig | 13 ------------- drivers/can/Kconfig | 2 +- 2 files changed, 1 insertion(+), 14 deletions(-) delete mode 100644 boards/shields/mcp2515/Kconfig.defconfig diff --git a/boards/shields/mcp2515/Kconfig.defconfig b/boards/shields/mcp2515/Kconfig.defconfig deleted file mode 100644 index fddd5ae1fb4..00000000000 --- a/boards/shields/mcp2515/Kconfig.defconfig +++ /dev/null @@ -1,13 +0,0 @@ -# Copyright (c) 2019 Linaro Limited -# SPDX-License-Identifier: Apache-2.0 - -if SHIELD_DFROBOT_CAN_BUS_V2_0 || SHIELD_KEYESTUDIO_CAN_BUS_KS0411 - -if CAN - -config CAN_INIT_PRIORITY - default 80 - -endif # CAN - -endif # SHIELD_DFROBOT_CAN_BUS_V2_0 || SHIELD_KEYESTUDIO_CAN_BUS_KS0411 diff --git a/drivers/can/Kconfig b/drivers/can/Kconfig index c006d468ec0..213b23eb639 100644 --- 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.