[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB8PR04MB6795064F932CF60033514367E6350@DB8PR04MB6795.eurprd04.prod.outlook.com>
Date: Mon, 28 Sep 2020 08:36:03 +0000
From: Joakim Zhang <qiangqing.zhang@....com>
To: Marc Kleine-Budde <mkl@...gutronix.de>,
"linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
Pankaj Bansal <pankaj.bansal@....com>
CC: dl-linux-imx <linux-imx@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH linux-can-next/flexcan 1/4] can: flexcan: initialize all
flexcan memory for ECC function
> -----Original Message-----
> From: Marc Kleine-Budde <mkl@...gutronix.de>
> Sent: 2020年9月28日 16:21
> To: Joakim Zhang <qiangqing.zhang@....com>; linux-can@...r.kernel.org;
> Pankaj Bansal <pankaj.bansal@....com>
> Cc: dl-linux-imx <linux-imx@....com>; netdev@...r.kernel.org
> Subject: Re: [PATCH linux-can-next/flexcan 1/4] can: flexcan: initialize all flexcan
> memory for ECC function
>
> On 9/28/20 9:58 AM, Joakim Zhang wrote:
> >> Can someone check the vf610, too?
> >
> > I check the VF610 RM just now, indeed it has ECC feature, there is also a
> NOTE in "12.1.4.13 Detection and Correction of Memory Errors" section:
> >
> > All FlexCAN memory must be initialized before starting its operation
> > in order to have the parity bits in memory properly updated. The
> > WRMFRZ bit in Control 2 Register (CTRL2) grants write access to all
> > memory positions from 0x080 to 0xADF.
>
> Sounds good.
Could I send out a V3 to review firstly, then wait Pankaj have time to do the test?
Best Regards,
Joakim Zhang
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung West/Dortmund | Phone: +49-231-2826-924 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists