From a66c30d689a8371499275b2d145a271600ac435b Mon Sep 17 00:00:00 2001 From: Henrik Brix Andersen Date: Tue, 2 Jan 2024 23:45:08 +0100 Subject: [PATCH] doc: releases: migration-guide: 3.6: removal of run-time CAN RTR filter Add a note about the removal of the CAN_FILTER_DATA and CAN_FILTER_RTR flags from the CAN controller driver API. Signed-off-by: Henrik Brix Andersen --- doc/releases/migration-guide-3.6.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/releases/migration-guide-3.6.rst b/doc/releases/migration-guide-3.6.rst index 434bc9368c5..fe753faa12b 100644 --- a/doc/releases/migration-guide-3.6.rst +++ b/doc/releases/migration-guide-3.6.rst @@ -146,6 +146,14 @@ Device Drivers and Device Tree * The main Kconfig option was renamed from ``CONFIG_CAN_NATIVE_POSIX_LINUX`` to :kconfig:option:`CONFIG_CAN_NATIVE_LINUX`. +* The ``CAN_FILTER_DATA`` and ``CAN_FILTER_RTR`` flags for filtering between Data and Remote + Transmission Request (RTR) frames were removed since not all CAN controllers implement support for + individual RX filtering based on the RTR bit. Applications can now use + :kconfig:option:`CONFIG_CAN_ACCEPT_RTR` to either accept incoming RTR frames matching CAN filters + or reject all incoming CAN RTR frames (the default). When :kconfig:option:`CONFIG_CAN_ACCEPT_RTR` + is enabled, applications can still filter between Data and RTR frames in their receive callback + functions as needed. + Power Management ================