drivers: can: remove option for configuring CAN-FD max DLC
Remove the Kconfig option for configuring the maximum value of the CAN-FD Data Length Code in order to ensure standard compliance. Allowing users to configure the max DLC allows the user to save a number of bytes per CAN frame in RAM, but it also renders the Zephyr CAN-FD implementation non-compliant with the CAN-FD standard. There are no guarantees that a Zephyr CAN-FD node will not receive a CAN frame with a DLC higher than the Kconfig limit, which opens up for all sorts of bugs when trying to handle received CAN-FD frames. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
This commit is contained in:
parent
c3c1bc1ae5
commit
c11326300f
2 changed files with 3 additions and 25 deletions
|
@ -54,18 +54,6 @@ config CAN_FD_MODE
|
|||
help
|
||||
Enable CAN-FD compatible API
|
||||
|
||||
if CAN_FD_MODE
|
||||
|
||||
config CANFD_MAX_DLC
|
||||
int "Max data length code in CAN frames"
|
||||
range 8 15
|
||||
default 15
|
||||
help
|
||||
Maximum allowed DLC in a CAN frame. This parameter sets the
|
||||
data buffer size in a CAN frame and is therefore only used to
|
||||
optimize memory consumption.
|
||||
endif # CAN_FD_MODE
|
||||
|
||||
config CAN_RX_TIMESTAMP
|
||||
bool "Receiving timestamps"
|
||||
depends on CAN_HAS_RX_TIMESTAMP
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue