can: kvaser_usb: CAN clock frequency regression
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | can: kvaser_usb: replace run-time checks with struct kvaser_usb_driver_infodrivers/ drivers/ drivers/ | +173 | 0 replies | |
| 2/3 | can: kvaser_usb: kvaser_usb_leaf: fix CAN clock frequency regressiondrivers/ drivers/ drivers/ | +38 | 0 replies | |
| 3/3 | can: kvaser_usb: kvaser_usb_leaf: fix bittiming limitsdrivers/ drivers/ drivers/ | +47 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 5.15 0/3] can: kvaser_usb: CAN clock frequency regression
Backport of upstream patch series [1].
When fixing the CAN clock frequency,fb12797ab1fe ("can: kvaser_usb: get CAN clock frequency from device"), I introduced a regression.
For Leaf devices based on M32C, the firmware expects bittiming parameters calculated for 16MHz clock. Regardless of the actual clock frequency.
This regression affects M32C based Leaf devices with non-16MHz clock.
Also correct the bittiming constants in kvaser_usb_leaf.c, where the limits are different depending on which firmware/device being used.
[1]
https://lore.kernel.org/linux-can/[email protected]/
Jimmy Assarsson (3):
can: kvaser_usb: replace run-time checks with struct
kvaser_usb_driver_info
can: kvaser_usb: kvaser_usb_leaf: fix CAN clock frequency regression
can: kvaser_usb: kvaser_usb_leaf: fix bittiming limits
drivers/net/can/usb/kvaser_usb/kvaser_usb.h | 25 +- .../net/can/usb/kvaser_usb/kvaser_usb_core.c | 286 ++++++++++-------- .../net/can/usb/kvaser_usb/kvaser_usb_hydra.c | 4 +- .../net/can/usb/kvaser_usb/kvaser_usb_leaf.c | 119 ++++---- 4 files changed, 244 insertions(+), 190 deletions(-)
Signature · 1 line
2.36.1