[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141107084051.GB23086@shlinux1.ap.freescale.net>
Date: Fri, 7 Nov 2014 16:40:52 +0800
From: Dong Aisheng <b29396@...escale.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>
CC: Oliver Hartkopp <socketcan@...tkopp.net>,
<linux-can@...r.kernel.org>, <wg@...ndegger.com>,
<varkabhadram@...il.com>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: M_CAN message RAM initialization AppNote - was: Re: [PATCH V3
3/3] can: m_can: workaround for transmit data less than 4 bytes
On Thu, Nov 06, 2014 at 01:47:20PM +0100, Marc Kleine-Budde wrote:
> On 11/06/2014 01:33 PM, Oliver Hartkopp wrote:
> >> So i'm not sure memset() the entire TX FIFO element is neccesary...
> >
> > It's no big deal - so we should be defensive here.
> > And memset() is not working as Marc pointed out in another mail.
> >
> > So we would need to loop with
> >
> > m_can_fifo_write(priv, 0, M_CAN_FIFO_DATA(i), 0x0);
> >
> >>
> >> Do you think we could keep the current solution firstly and updated later
> >> if needed?
> >
> > No :-)
> >
> > I would like to have all data bytes to be written at startup.
>
> Me, too. As this happens only once during ifconfig up it should not hurt
> performance, either send an incremental or new patch. I'll sort it out.
>
I will send a new patch for this.
Regards
Dong Aisheng
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Industrial Linux Solutions | Phone: +49-231-2826-924 |
> Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists