can: stm32fd: correct timing min/max for prop_seg and sjw

This commit changes the timing_min_data prop_seg
initialization of st,stm32-fdcan drier to zero.
Additionally the nominal sync jump width limits
are also adopted to new values 1 and 128.

This was not tested until recently and therefore
caused the can timing test to fail on stm32g4
after PR #44197 got merged.

Signed-off-by: Thomas Stranger <thomas.stranger@outlook.com>
This commit is contained in:
Thomas Stranger 2022-03-30 16:00:50 +02:00 committed by Carles Cufí
commit c128a89690

View file

@ -191,14 +191,14 @@ static const struct can_driver_api can_api_funcs = {
.get_max_filters = can_mcan_get_max_filters,
.set_state_change_callback = can_stm32fd_set_state_change_callback,
.timing_min = {
.sjw = 0x7f,
.sjw = 0x01,
.prop_seg = 0x00,
.phase_seg1 = 0x01,
.phase_seg2 = 0x01,
.prescaler = 0x01
},
.timing_max = {
.sjw = 0x7f,
.sjw = 0x80,
.prop_seg = 0x00,
.phase_seg1 = 0x100,
.phase_seg2 = 0x80,
@ -207,7 +207,7 @@ static const struct can_driver_api can_api_funcs = {
#ifdef CONFIG_CAN_FD_MODE
.timing_min_data = {
.sjw = 0x01,
.prop_seg = 0x01,
.prop_seg = 0x00,
.phase_seg1 = 0x01,
.phase_seg2 = 0x01,
.prescaler = 0x01