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

53 lines
1.3 KiB
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
# CAN loopback device configuration options
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-19 00:19:35 +08:00
# Copyright (c) 2019 Alexander Wachter
# SPDX-License-Identifier: Apache-2.0
config CAN_LOOPBACK
bool "Loopback CAN driver"
help
This is a dummy driver that can only loopback messages.
if CAN_LOOPBACK
config CAN_LOOPBACK_DEV_NAME
string "CAN loopback device name"
default "CAN_LOOPBACK"
help
"Device name for the loopback device"
config CAN_MAX_FILTER
int "Maximum number of concurrent active filters"
drivers: can: loopback: Use thread to send frames. The loopback driver is a simple driver that can be used to test CAN subsystems. The actual implementation sends frames in the same thread that calls the send function. Some libraries have problems with that behavior. This PR implements a dedicated thread that calls the callback for the receiving functions and a msgq in between the sender and the TX thread. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2020-02-12 22:36:47 +08:00
default 16
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-19 00:19:35 +08:00
range 1 1024
help
Defines the array size of the filters.
Must be at least the size of concurrent reads.
drivers: can: loopback: Use thread to send frames. The loopback driver is a simple driver that can be used to test CAN subsystems. The actual implementation sends frames in the same thread that calls the send function. Some libraries have problems with that behavior. This PR implements a dedicated thread that calls the callback for the receiving functions and a msgq in between the sender and the TX thread. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2020-02-12 22:36:47 +08:00
config CAN_LOOPBACK_TX_THREAD_STACK_SIZE
int "TX thread stack size"
default 256
help
Stack size of the TX thread.
The TX thread calls the callbacks of the receiver
if the filter matches.
config CAN_LOOPBACK_TX_THREAD_PRIORITY
int "TX thread priority"
default 2
help
Priority of the TX thread.
The TX thread calls the callbacks of the receiver
if the filter matches.
config CAN_LOOPBACK_TX_MSGQ_SIZE
int "TX message queue size"
default 16
help
Number of TX frames that can be buffered.
The send functions puts frame int this queue and TX thread takes the
messages from this msgq and calls the respective receiver if the
filter matches.
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-19 00:19:35 +08:00
endif # CAN_LOOPBACK