0f36f1a3ee
Restructure the Bosch M_CAN driver backend to use per-instance Message RAM configuration. This removes the need for a common, artificial "can" devicetree node for SoCs with multiple Bosch M_CAN-based CAN controllers and allows for per-instance configuration of the number of e.g. standard (11-bit) and extended (29-bit) filter elements. As part of the restructure, software handling of CAN filter flags was moved from per-flags bitfields to per-filter bitfields, solving an issue when using more than 32 standard (11-bit) filter elements or more than 16 extended (29-bit) filter elements. Fixes: #42030, #53417 Signed-off-by: Henrik Brix Andersen <hebad@vestas.com> |
||
---|---|---|
.. | ||
atmel,sam-can.yaml | ||
atmel,sam0-can.yaml | ||
bosch,m_can-base.yaml | ||
can-controller.yaml | ||
can-fd-controller.yaml | ||
espressif,esp32-twai.yaml | ||
kvaser,pcican.yaml | ||
microchip,mcp2515.yaml | ||
nxp,flexcan-fd.yaml | ||
nxp,flexcan.yaml | ||
nxp,lpc-mcan.yaml | ||
nxp,s32-canxl.yaml | ||
renesas,rcar-can.yaml | ||
st,stm32-can.yaml | ||
st,stm32-fdcan.yaml | ||
st,stm32h7-fdcan.yaml | ||
zephyr,can-loopback.yaml | ||
zephyr,fake-can.yaml | ||
zephyr,native-posix-linux-can.yaml |