]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
can: tcan4x5x: fix bittiming const, use common bittiming from m_can driver
authorMarc Kleine-Budde <mkl@pengutronix.de>
Tue, 15 Dec 2020 10:32:38 +0000 (11:32 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 17 Jan 2021 13:05:35 +0000 (14:05 +0100)
commit3b68980596fb4edcf13daa91dedfd6a95e022ca8
tree50fb626df1c072cbbae4343d3596e1374e2017aa
parentb77e0283efdc2c79d392cf8d7ae9cd5142427199
can: tcan4x5x: fix bittiming const, use common bittiming from m_can driver

commit aee2b3ccc8a63d1cd7da6a8a153d1f3712d40826 upstream.

According to the TCAN4550 datasheet "SLLSF91 - DECEMBER 2018" the tcan4x5x has
the same bittiming constants as a m_can revision 3.2.x/3.3.0.

The tcan4x5x chip I'm using identifies itself as m_can revision 3.2.1, so
remove the tcan4x5x specific bittiming values and rely on the values in the
m_can driver, which are selected according to core revision.

Fixes: 5443c226ba91 ("can: tcan4x5x: Add tcan4x5x driver to the kernel")
Cc: Dan Murphy <dmurphy@ti.com>
Reviewed-by: Sean Nyekjaer <sean@geanix.com>
Link: https://lore.kernel.org/r/20201215103238.524029-3-mkl@pengutronix.de
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/net/can/m_can/tcan4x5x.c