can: tcan4x5x: Fix register range of first two blocks

According to the datasheet 0x10 is the last register in the first block,
not register 0x2c.

The datasheet lists the last register of the second block as 0x830, not
0x83c.

Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
Link: https://lore.kernel.org/all/20221206115728.1056014-11-msp@baylibre.com
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

diff --git a/drivers/net/can/m_can/tcan4x5x-regmap.c b/drivers/net/can/m_can/tcan4x5x-regmap.c
index 26e212b8ca7a6af86ba4467f2b54d16f17db112b..33aed989e42acd6c4a7a28b41559be9545e2fd3b 100644 (file)
--- a/drivers/net/can/m_can/tcan4x5x-regmap.c
+++ b/drivers/net/can/m_can/tcan4x5x-regmap.c
@@ -91,8 +91,8 @@ static int tcan4x5x_regmap_read(void *context,
 }
 
 static const struct regmap_range tcan4x5x_reg_table_yes_range[] = {
-       regmap_reg_range(0x0000, 0x002c),       /* Device ID and SPI Registers */
-       regmap_reg_range(0x0800, 0x083c),       /* Device configuration registers and Interrupt Flags*/
+       regmap_reg_range(0x0000, 0x0010),       /* Device ID and SPI Registers */
+       regmap_reg_range(0x0800, 0x0830),       /* Device configuration registers and Interrupt Flags*/
        regmap_reg_range(0x1000, 0x10fc),       /* M_CAN */
        regmap_reg_range(0x8000, 0x87fc),       /* MRAM */
 };