OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/can/Kconfig.mcp2515

37 lines
857 B
Plaintext
Raw 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 20:45:29 +08:00
# MCP2515 CAN configuration options
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 14:23:20 +08:00
# Copyright (c) 2018 Karsten Koenig
# SPDX-License-Identifier: Apache-2.0
config CAN_MCP2515
bool "MCP2515 CAN Driver"
depends on SPI
help
Enable MCP2515 CAN Driver
if CAN_MCP2515
config CAN_MCP2515_INT_THREAD_STACK_SIZE
int "Stack size for interrupt handler"
default 512
help
Size of the stack used for internal thread which is ran for
interrupt handling and incoming packets.
config CAN_MCP2515_INT_THREAD_PRIO
int "Priority for interrupt handler"
default 2
help
Priority level of the internal thread which is ran for
interrupt handling and incoming packets.
drivers: can: mcp2515: Remove MCP2515 specifics CAN_MCP2515_MAX_FILTER is not needed anymore and was probably just a misunderstanding. Aligned it with the other CAN drivers. This also was the last difference in the mcp2515 specific config for the can sample, so that can be deleted as well. Signed-off-by: Karsten Koenig <karsten.koenig.030@gmail.com>
2021-01-09 01:48:17 +08:00
config CAN_MAX_FILTER
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 14:23:20 +08:00
int "Maximum number of concurrent active filters"
default 5
range 1 32
help
Defines the array size of the callback/msgq pointers.
Must be at least the size of concurrent reads.
endif # CAN_MCP2515