From 00eae2dffd244246b372dbb48f042dac9fbdddc5 Mon Sep 17 00:00:00 2001 From: Henrik Brix Andersen Date: Tue, 9 Apr 2024 06:35:04 +0000 Subject: [PATCH] doc: releases: release-notes: 3.7: can_get_{min,max}_bitrate() changes Mention the new can_get_bitrate_min() and can_get_bitrate_max() CAN controller API functions along with the deprecating of the existing can_get_min_bitrate() and can_get_max_bitrate(). Signed-off-by: Henrik Brix Andersen --- doc/releases/release-notes-3.7.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/releases/release-notes-3.7.rst b/doc/releases/release-notes-3.7.rst index 4a547137fae..10b0a99a729 100644 --- a/doc/releases/release-notes-3.7.rst +++ b/doc/releases/release-notes-3.7.rst @@ -87,6 +87,10 @@ Drivers and Sensors * Deprecated the :c:func:`can_calc_prescaler` API function, as it allows for bitrate errors. Bitrate errors between nodes on the same network leads to them drifting apart after the start-of-frame (SOF) synchronization has taken place, leading to bus errors. + * Added :c:func:`can_get_bitrate_min` and :c:func:`can_get_bitrate_max` for retrieving the minimum + and maximum supported bitrate for a given CAN controller/CAN transceiver combination, reflecting + that retrieving the bitrate limits can no longer fail. Deprecated the existing + :c:func:`can_get_min_bitrate` and :c:func:`can_get_max_bitrate` API functions. * Extended support for automatic sample point location to also cover :c:func:`can_calc_timing` and :c:func:`can_calc_timing_data`. * Added optional ``min-bitrate`` devicetree property for CAN transceivers.