The M_CAN's configuration interface of v3.3.0 is compatible to v3.2.x.
Therefore, version 3.3.x is handled like 3.2.x.
Signed-off-by: Mario Hüttel <mario.huettel@xxxxxxx>
---
drivers/net/can/m_can/m_can.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index 9b449400..0657094f 100644
--- a/drivers/net/can/m_can/m_can.c
+++ b/drivers/net/can/m_can/m_can.c
@@ -1110,7 +1110,7 @@ static void m_can_chip_config(struct net_device *dev)
cccr |= CCCR_CME_CANFD_BRS << CCCR_CME_SHIFT;
} else {
- /* Version 3.1.x or 3.2.x */
+ /* Version 3.1.x or 3.2.x or 3.3.x */
cccr &= ~(CCCR_TEST | CCCR_MON | CCCR_BRSE | CCCR_FDOE |
CCCR_NISO);
@@ -1289,6 +1289,7 @@ static int m_can_dev_setup(struct platform_device *pdev, struct net_device *dev,
&m_can_data_bittiming_const_31X;
break;
case 32:
+ case 33:
priv->can.bittiming_const = &m_can_bittiming_const_31X;
priv->can.data_bittiming_const =
&m_can_data_bittiming_const_31X;
--
2.19.0
