patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 7 Packages Projects Releases Wiki Activity

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

Browse source 
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 <hebad@vestas.com>
This commit is contained in:
Henrik Brix Andersen 2023-06-01 18:21:04 +02:00 committed by Anas Nashif
parent b7160271e8
commit b12eb78f35
2 changed files with 1 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
boards/shields/mcp2515/Kconfig.defconfig
View file

@ -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

2
drivers/can/Kconfig
View file

@ -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.