can: m_can: move Message RAM initialization to function
authorQuentin Schulz <quentin.schulz@free-electrons.com>
Fri, 5 May 2017 13:50:30 +0000 (15:50 +0200)
committerMarc Kleine-Budde <mkl@pengutronix.de>
Thu, 18 May 2017 08:32:48 +0000 (10:32 +0200)
commit6a792e8158a2597418a0833c7e350328e209f318
tree01ffc6baab01d2420f763d5781f3ffaedf0ca0e4
parent1fc4d180b3c6bed0e7f5160bcd553aec89594962
can: m_can: move Message RAM initialization to function

To avoid possible ECC/parity checksum errors when reading an
uninitialized buffer, the entire Message RAM is initialized when probing
the driver. This initialization is done in the same function reading the
Device Tree properties.

This patch moves the RAM initialization to a separate function so it can
be called separately from device initialization from Device Tree.

Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
drivers/net/can/m_can/m_can.c