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/CMakeLists.txt

9 lines
319 B
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
drivers: can: rework can_attach_msgq can_attach_msgq can be implemented as a wrapper of can_attach_isr. This is implemented as a common function for all drives and reduces the complexity of the specific drivers. Since this is common to multi instances of drivers too, it is removed from the API struct. Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-03-18 05:51:13 +08:00
zephyr_sources_ifdef(CONFIG_CAN can_common.c)
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
zephyr_sources_ifdef(CONFIG_CAN_LOOPBACK can_loopback.c)
drivers: can: rename drivers to can_<dev name> The filenames of the can drivers were not consisten. Changed them to can_<dev name> Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-04-20 00:23:17 +08:00
zephyr_sources_ifdef(CONFIG_CAN_MCP2515 can_mcp2515.c)
zephyr_sources_ifdef(CONFIG_CAN_STM32 can_stm32.c)
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
zephyr_sources_ifdef(CONFIG_USERSPACE can_handlers.c)