michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/can/Kconfig

128 lines
3.3 KiB
Plaintext
Raw Permalink Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 13:45:29 +01:00
# CAN configuration options
drivers: can: Add Kconfig for CAN driver This commit adds the Kconfig for generic CAN drivers. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2018-05-03 10:48:02 +02:00
# Copyright (c) 2018 Alexander Wachter
# SPDX-License-Identifier: Apache-2.0
#
# CAN options
#
menuconfig CAN
drivers: kconfig: unify menuconfig title strings Unify the drivers/*/Kconfig menuconfig title strings to the format "<class> [(acronym)] [bus] drivers". Including both the full name of the driver class and an acronym makes menuconfig more user friendly as some of the acronyms are less well-known than others. It also improves Kconfig search, both via menuconfig and via the generated Kconfig documentation. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-03-27 14:55:23 +02:00
bool "Controller Area Network (CAN) drivers"
drivers: can: Add Kconfig for CAN driver This commit adds the Kconfig for generic CAN drivers. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2018-05-03 10:48:02 +02:00
help
Enable CAN Driver Configuration
if CAN
drivers: can: move to new logger Move to new logger subsystem. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-17 19:13:20 +02:00
module = CAN
module-str = CAN
source "subsys/logging/Kconfig.template.log_config"
drivers: can: Add Kconfig for CAN driver This commit adds the Kconfig for generic CAN drivers. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2018-05-03 10:48:02 +02:00
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>
2021-10-20 21:36:07 +02:00
config CAN_INIT_PRIORITY
drivers: can: socketCAN: Move socket code to own file Move the code for socket instanciation from each driver to a generic driver, that makes an instance of a socketCAN net device for the chosen node. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2022-01-16 14:35:07 +01:00
int "CAN driver init priority"
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 <hebad@vestas.com>
2023-06-01 18:21:04 +02:00
default 80
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>
2021-10-20 21:36:07 +02:00
help
CAN driver device initialization priority.
drivers: can: set default initial bitrates via Kconfig Set the default initial bitrates globally via Kconfig. The initial bitrates can still be overridden using the "bus-speed" and "bus-speed-data" devicetree properties. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2024-04-24 11:09:15 +02:00
config CAN_DEFAULT_BITRATE
int "Default CAN bitrate"
default 125000
help
Default initial CAN bitrate in bits/s. This can be overridden per CAN controller using the
"bus-speed" devicetree property.
config CAN_DEFAULT_BITRATE_DATA
int "Default CAN data phase bitrate"
default 1000000
depends on CAN_FD_MODE
help
Default initial CAN data phase bitrate in bits/s. This can be overridden per CAN controller
using the "bus-speed-data" devicetree property.
drivers: can: Add CAN shell Implement a CAN shell. With this shell you can send messages, attach and tetach filters. Messages that match the attached filters are printed to the shell. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-04-24 20:09:34 +02:00
config CAN_SHELL
drivers: can: rewrite the CAN shell module Rewrite the CAN shell module to catch up with the added CAN controller API functionality. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-08-26 12:50:16 +02:00
bool "CAN shell"
drivers: can: Add CAN shell Implement a CAN shell. With this shell you can send messages, attach and tetach filters. Messages that match the attached filters are printed to the shell. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-04-24 20:09:34 +02:00
depends on SHELL
drivers: can: shell: convert from can_attach_workq() to triggered work Convert the CAN shell from using can_attach_workq() to using can_attach_msgq() and triggered work via k_work_poll_submit(). Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2021-12-16 12:13:33 +01:00
select POLL
drivers: can: Add CAN shell Implement a CAN shell. With this shell you can send messages, attach and tetach filters. Messages that match the attached filters are printed to the shell. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-04-24 20:09:34 +02:00
help
Enable CAN Shell for testing.
drivers: can: rewrite the CAN shell module Rewrite the CAN shell module to catch up with the added CAN controller API functionality. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-08-26 12:50:16 +02:00
if CAN_SHELL
config CAN_SHELL_TX_QUEUE_SIZE
int "CAN shell transmit queue size"
default 5
range 1 256
help
Maximum number of events in the CAN shell transmit queue.
config CAN_SHELL_RX_QUEUE_SIZE
int "CAN shell receive queue size"
default 5
range 1 256
help
Maximum number of CAN frames in the CAN shell receive queue.
endif # CAN_SHELL
drivers: can: add statistics support Add CAN controller device statistics support. Initially the following per-device statistics are supported: - Dominant bit transmission errors - Recessive bit transmission errors - Bit stuffing errors - CRC errors - Format errors - Acknowledge errors Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-11 15:03:32 +01:00
config CAN_STATS
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 12:05:12 +01:00
bool "CAN controller device statistics"
drivers: can: add statistics support Add CAN controller device statistics support. Initially the following per-device statistics are supported: - Dominant bit transmission errors - Recessive bit transmission errors - Bit stuffing errors - CRC errors - Format errors - Acknowledge errors Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-11 15:03:32 +01:00
depends on STATS
help
Enable CAN controller device statistics.
drivers: can: remove run-time RTR filtering, add build-time RTR filter A growing number of CAN controllers do not have support for individual RX hardware filters based on the Remote Transmission Request (RTR) bit. This leads to various work-arounds on the driver level mixing hardware and software filtering. As the use of RTR frames is discouraged by CAN in Automation (CiA) - and not even supported by newer standards, e.g. CAN FD - this often leads to unnecessary overhead, added complexity, and worst-case to non-portable behavior between various CAN controller drivers. Instead, move to a simpler approach where the ability to accept/reject RTR frames is globally configured via Kconfig. By default, all incoming RTR frames are rejected at the driver level, a setting which can be supported in hardware by most in-tree CAN controllers drivers. Legacy applications or protocol implementations, where RTR reception is required, can now select CONFIG_CAN_ACCEPT_RTR to accept incoming RTR frames matching added CAN filters. These applications or protocols will need to distinguish between RTR and data frames in their respective CAN RX frame handling routines. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-12-15 13:36:18 +01:00
config CAN_ACCEPT_RTR
bool "Accept Remote Transmission Requests (RTR) frames"
help
Accept incoming Remote Transmission Request (RTR) frames matching CAN RX filters. Unless
enabled, all incoming Remote Transmission Request (RTR) frames are rejected at the driver
level.
drivers: can: Implement Bosch M_CAN driver Implementation of the Bosch M_CAN IP driver. This driver is just the base for a specific SoC implementation. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2021-02-11 20:07:04 +01:00
config CAN_FD_MODE
drivers: can: rework support for manual bus-off recovery Since all CAN controllers drivers seem to support automatic recovery (for any future drivers for hardware without this hardware capability this can easily be implemented in the driver), change the Zephyr CAN controller API policy to: - Always enable automatic bus recovery upon driver initialization, regardless of Kconfig options. Since CAN controllers are initialized in "stopped" state, no unwanted bus-off recovery will be started at this point. - Invert and rename the Kconfig CONFIG_CAN_AUTO_BUS_OFF_RECOVERY, which is enabled by default, to CONFIG_CAN_MANUAL_RECOVERY_MODE, which is disabled by default. Enabling CONFIG_CAN_MANUAL_RECOVERY_MODE=y enables support for the can_recover() API function and a new manual recovery mode (see next bullet). Keeping this guarded by Kconfig allows keeping the flash footprint down for applications not using manual bus-off recovery. - Introduce a new CAN controller operational mode CAN_MODE_MANUAL_RECOVERY. Support for this is only enabled if CONFIG_CAN_MANUAL_RECOVERY_MODE=y. Having this as a mode allows applications to inquire whether the CAN controller supports manual recovery mode via the can_get_capabilities() API function and either fail or rely on automatic recovery - and it allows CAN controller drivers not supporting manual recovery mode to fail early in can_set_mode() during application startup instead of failing when can_recover() is called at a later point in time. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2024-02-14 22:38:34 +01:00
bool "CAN FD support"
drivers: can: Rework can_configure API The previous API can't change the sampling-point and only allowed bitrates that fit the time segments. The new API allows for shifting the sampling-point and adjusts the number of time quantum in a bit to all more possible bitrates. The functions to calculate the timings are moved to the can_common file. They can be used for all drivers. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2020-04-27 18:58:05 +02:00
help
drivers: can: unify spelling of CAN Flexible Data-rate abbreviation Unify spelling of CAN Flexible Data-rate abbreviation to "CAN FD" instead of "CAN-FD". The former aligns with the CAN in Automation (CiA) recommendation. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-10-31 10:09:38 +01:00
Enable CAN FD support. Not all CAN controllers support CAN FD.
drivers: can: Rework can_configure API The previous API can't change the sampling-point and only allowed bitrates that fit the time segments. The new API allows for shifting the sampling-point and adjusts the number of time quantum in a bit to all more possible bitrates. The functions to calculate the timings are moved to the can_common file. They can be used for all drivers. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2020-04-27 18:58:05 +02:00
drivers: can: rework support for manual bus-off recovery Since all CAN controllers drivers seem to support automatic recovery (for any future drivers for hardware without this hardware capability this can easily be implemented in the driver), change the Zephyr CAN controller API policy to: - Always enable automatic bus recovery upon driver initialization, regardless of Kconfig options. Since CAN controllers are initialized in "stopped" state, no unwanted bus-off recovery will be started at this point. - Invert and rename the Kconfig CONFIG_CAN_AUTO_BUS_OFF_RECOVERY, which is enabled by default, to CONFIG_CAN_MANUAL_RECOVERY_MODE, which is disabled by default. Enabling CONFIG_CAN_MANUAL_RECOVERY_MODE=y enables support for the can_recover() API function and a new manual recovery mode (see next bullet). Keeping this guarded by Kconfig allows keeping the flash footprint down for applications not using manual bus-off recovery. - Introduce a new CAN controller operational mode CAN_MODE_MANUAL_RECOVERY. Support for this is only enabled if CONFIG_CAN_MANUAL_RECOVERY_MODE=y. Having this as a mode allows applications to inquire whether the CAN controller supports manual recovery mode via the can_get_capabilities() API function and either fail or rely on automatic recovery - and it allows CAN controller drivers not supporting manual recovery mode to fail early in can_set_mode() during application startup instead of failing when can_recover() is called at a later point in time. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2024-02-14 22:38:34 +01:00
config CAN_MANUAL_RECOVERY_MODE
bool "Manual bus-off recovery support"
help
Enable support for manual (non-automatic) recovery from bus-off state. Not all CAN
controllers support manual recovery mode.
can: Add RX timestamp to zcan_frame This commit introduces a timestamp for received CAN frames. The timestamp is optional and can be activated via Kconfig. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-07-24 15:34:51 +02:00
config CAN_RX_TIMESTAMP
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 12:05:12 +01:00
bool "Receiving timestamps"
can: Add RX timestamp to zcan_frame This commit introduces a timestamp for received CAN frames. The timestamp is optional and can be activated via Kconfig. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-07-24 15:34:51 +02:00
help
This option enables a timestamp value of the CAN free running timer.
The value is incremented every bit time and starts when the controller
drivers: can: remove CAN_HAS_RX_TIMESTAMP Kconfig helper Remove the CAN_HAS_RX_TIMESTAMP Kconfig helper symbol in order to allow enabling CAN RX timestamps in the API regardless of driver support. This simplifies application prj.conf settings across board supporting/not supporting RX timestamps considerably. CAN drivers not supporting RX timestamps already initialize the timestamp to 0 for received frames. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-01-24 12:02:34 +01:00
is initialized. Not all CAN controllers support timestamps.
can: Add RX timestamp to zcan_frame This commit introduces a timestamp for received CAN frames. The timestamp is optional and can be activated via Kconfig. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-07-24 15:34:51 +02:00
drivers: can: add support for configuring CAN emulation in QEMU Add support for configuring CAN emulation support in QEMU. For now, the only supported CAN controller is the single-channel Kvaser PCIcan PCI card. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-10-21 10:33:27 +02:00
config CAN_QEMU_IFACE_NAME
string "SocketCAN interface name for QEMU"
default ""
depends on QEMU_TARGET
help
The SocketCAN interface name for QEMU. This value, if set, is given as "if" parameter to
the "-object can-host-socketcan" qemu command line option. The CAN interface must be
configured before starting QEMU.
drivers: can: Add frontend for Atmel SAM M_CAN controller This commit adds a frontend for the generic Bosch m_can driver for Atmel SAM series. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2022-01-09 22:25:58 +01:00
source "drivers/can/Kconfig.sam"
sam: can: CAN driver for SAM0 socs Driver was based on can_sam. SAMC21 has only 1 interrupt for one can "output", so can interrupt has to executes two lines of interrupts. CAN is configured to use OSC48M clock via GLCK7. GLCK7 is set by divider configured from dts. Signed-off-by: Kamil Serwus <kserwus@gmail.com>
2022-11-16 20:27:33 +01:00
source "drivers/can/Kconfig.sam0"
drivers: can: Add CAN driver support for STM32 This commit adds low level driver support for STM32 micro controllers. It is tested on stm32f072b in loopback and normal mode. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2018-05-03 10:59:12 +02:00
source "drivers/can/Kconfig.stm32"
drivers: can: add support for the NXP Kinetis FlexCAN controller Add MCUX driver shim for the NXP Kinetis FlexCAN CAN bus controller. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2019-06-06 20:42:06 +02:00
source "drivers/can/Kconfig.mcux"
drivers: can: mcp2515: Add driver for MCP2515 CAN controller The MCP2515 is a CAN controller that can be connected via SPI to an host MCU. This driver adds support for the MCP2515 as a new driver in the CAN subsystem. As it is a SPI peripheral it uses a thread for its interrupt handling and the received message filtering is done inside this interrupt thread, as the MCP2515 filter capabilities are not sufficient for the Zephyr CAN interface. The driver was validated with an external CAN logger and the adjusted CAN sample application. Signed-off-by: Karsten Koenig <karsten.koenig.030@gmail.com>
2018-06-12 08:23:20 +02:00
source "drivers/can/Kconfig.mcp2515"
drivers: can: Implement Bosch M_CAN driver Implementation of the Bosch M_CAN IP driver. This driver is just the base for a specific SoC implementation. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2021-02-11 20:07:04 +01:00
source "drivers/can/Kconfig.mcan"
drivers: can: Add Renesas R-Car driver This driver is for classic CAN, it makes use of CAN interface in FIFO mode. This driver support Standard ID as well as Extended ID. Tested on H3ULCB, Ebisu platform, with external adapter and in loopback mode. Signed-off-by: Julien Massot <julien.massot@iot.bzh>
2021-05-10 10:19:57 +02:00
source "drivers/can/Kconfig.rcar"
drivers: can: support for Nuvoton numaker series Add Nuvoton numaker series can-fd controller based on mcan. Signed-off-by: cyliang tw <cyliang@nuvoton.com>
2023-10-24 13:01:32 +02:00
source "drivers/can/Kconfig.numaker"
drivers: can: Add loopback driver This commit implements a CAN loopback device. This device is used for testing when no CAN controller is available on the hardware. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-03-18 17:19:35 +01:00
source "drivers/can/Kconfig.loopback"
drivers: can: drop POSIX from the native Linux SocketCAN driver name Rename the native Linux SocketCAN driver to reflect that it can can now be used in both native_posix and native_sim (with or without an embedded C-library). Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-12-10 22:03:41 +01:00
source "drivers/can/Kconfig.native_linux"
drivers: can: add NXP SJA1000 common driver backend Add a common driver backend for NXP SJA1000 compatible CAN controllers. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-06-22 16:11:44 +02:00
source "drivers/can/Kconfig.sja1000"
drivers: can: add ESP32 TWAI CAN controller driver Add ESP32 TWAI CAN controller driver. The TWAI is register-compatible with the NXP SJA1000 CAN controller. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-06-22 16:14:34 +02:00
source "drivers/can/Kconfig.esp32"
drivers: can: add driver for the Kvaser PCIcan CAN controller PCI card Add driver for the Kvaser PCIcan CAN controller PCI card for use with QEMU. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-10-21 10:31:46 +02:00
source "drivers/can/Kconfig.kvaser"
drivers: can: make the fake CAN driver generally available Make the fake CAN controller driver available for use in tests outside of the CAN shell test. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-10-26 12:28:46 +02:00
source "drivers/can/Kconfig.fake"
drivers: can: support NXP S32 CANEXCEL This patch introduces support for NXP S32 CANEXCEL (CANXL) peripheral. CAN protocol supporting: - CAN classic - CAN FD Remote transmission request is not supported as this feature is not available on NXP S32 CANXL HAL. Signed-off-by: Cong Nguyen Huu <cong.nguyenhuu@nxp.com>
2022-11-30 02:47:14 +01:00
source "drivers/can/Kconfig.nxp_s32"
drivers: can: add tcan4x5x CAN controller driver Add driver for the TI TCAN4x5x series of CAN controllers. These CAN controllers are based on the Bosch M_CAN IP and interfaced via an SPI bus. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-08-29 13:54:03 +02:00
source "drivers/can/Kconfig.tcan4x5x"
drivers: can: mcp251xfd: Add driver This continue PR #31270. The updated changes are: - Updated to work with latest zephyr - Inplace reads/writes of registers - Batch read of RX messages when multiple messages can be read - FIFO abstraction of RX/TEF queues - Handle ivmif errors - Use READ_CRC for register reads - Use bitmasks instead of bitfield members - Rename mcp25xxfd to mcp251xfd - General cleanups Signed-off-by: Andriy Gelman <andriy.gelman@gmail.com>
2023-07-02 20:22:50 +02:00
source "drivers/can/Kconfig.mcp251xfd"
drivers: can: Add xmc4xxx CAN support Adds CAN drivers for XMC4xxx SoCs. XMC4xxx has multiple CAN nodes. The nodes share a common clock and a message object pool. The CAN nodes do not have a loopback mode. Instead there is an internal bus which can be used to exchange messages between nodes on the SoC. For this reason tests/samples which rely on the loopback feature have been disabled. Signed-off-by: Andriy Gelman <andriy.gelman@gmail.com>
2023-12-26 18:05:00 +01:00
source "drivers/can/Kconfig.xmc4xxx"
drivers: can: add NXP SJA1000 common driver backend Add a common driver backend for NXP SJA1000 compatible CAN controllers. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-06-22 16:11:44 +02:00
drivers: can: add generic GPIO controlled CAN transceiver driver Add generic driver for GPIO controlled CAN transceivers. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-28 15:16:50 +01:00
source "drivers/can/transceiver/Kconfig"
drivers: can: Add Kconfig for CAN driver This commit adds the Kconfig for generic CAN drivers. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2018-05-03 10:48:02 +02:00
endif # CAN
Copy permalink