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 <henrik@brixandersen.dk>
This commit is contained in:
parent
8eded2f76b
commit
00eae2dffd
1 changed files with 4 additions and 0 deletions
|
@ -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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue