zephyr

Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.

bluetooth bluetooth-le embedded embedded-c iot mcu microcontroller real-time rtos zephyr zephyr-rtos zephyros

History

Henrik Brix Andersen f8a88cdb27 drivers: can: use flags fields for can_frame and can_filter structs The can_frame and can_filter structs support a number of different flags (standard/extended CAN ID type, Remote Transmission Request, CAN-FD format, Bit Rate Switch, ...). Each of these flags is represented as a discrete bit in the given structure. This design pattern requires every user of these structs to initialize all of these flags to either 0 or 1, which does not scale well for future flag additions. Some of these flags have associated enumerations to be used for assignment, some do not. CAN drivers and protocols tend to rely on the logical value of the flag instead of using the enumeration, leading to a very fragile API. The enumerations are used inconsistently between the can_frame and can_filter structures, which further complicates the API. Instead, convert these flags to bitfields with separate flag definitions for the can_frame and can_filter structures. This API allows for future extensions without having to revisit existing users of the two structures. Furthermore, this allows driver to easily check for unsupported flags in the respective API calls. As this change leads to the "id_mask" field of the can_filter to be the only mask present in that structure, rename it to "mask" for simplicity. Fixes: #50776 Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>		3 years ago
..
isotp	drivers: can: use flags fields for can_frame and can_filter structs	3 years ago
CMakeLists.txt	modules: canopennode: move glue code to modules directory	4 years ago
Kconfig	modules: canopennode: move glue code to modules directory	4 years ago
Kconfig.canopen	modules: canopennode: move glue code to modules directory	4 years ago