From: David Jander <david@protonic.nl>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: RFC: [PATCH v2 1/2] can: flexcan: Correctly initialize mailboxes
Date: Wed, 3 Sep 2014 08:58:56 +0200 [thread overview]
Message-ID: <20140903085856.3a7e1e9a@archvile> (raw)
In-Reply-To: <1409670216-25674-2-git-send-email-mkl@pengutronix.de>
On Tue, 2 Sep 2014 17:03:35 +0200
Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> From: David Jander <david@protonic.nl>
>
> Apparently mailboxes may contain random data at startup, causing some of
> them being prepared for message reception. This causes overruns being
> missed or even confusing the IRQ check for trasmitted messages, increasing
> the transmit counter instead of the error counter.
>
> Signed-off-by: David Jander <david@protonic.nl>
> [mkl: adjust starting value of loop]
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> Changes since v1:
> - don't remove existing initialization of FLEXCAN_TX_BUF_ID
> - start loop at FLEXCAN_TX_BUF_ID + 1
>
> Marc
>
> drivers/net/can/flexcan.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/can/flexcan.c b/drivers/net/can/flexcan.c
> index 630c7bf..6ec49bd 100644
> --- a/drivers/net/can/flexcan.c
> +++ b/drivers/net/can/flexcan.c
> @@ -801,6 +801,7 @@ static int flexcan_chip_start(struct net_device *dev)
> struct flexcan_regs __iomem *regs = priv->base;
> int err;
> u32 reg_mcr, reg_ctrl;
> + int i;
>
> /* enable module */
> err = flexcan_chip_enable(priv);
> @@ -870,6 +871,11 @@ static int flexcan_chip_start(struct net_device *dev)
> /* Abort any pending TX, mark Mailbox as INACTIVE */
> flexcan_write(FLEXCAN_MB_CNT_CODE(0x4),
> ®s->cantxfg[FLEXCAN_TX_BUF_ID].can_ctrl);
> + /* Clear and invalidate all mailboxes first */
> + for (i = FLEXCAN_TX_BUF_ID + 1; i < ARRAY_SIZE(regs->cantxfg; i++) {
> + flexcan_write(FLEXCAN_MB_CNT_CODE(0),
> + ®s->cantxfg[i].can_ctrl);
> + }
>
> /* acceptance mask/acceptance code (accept everything) */
> flexcan_write(0x0, ®s->rxgmask);
This assumes that FLEXCAN_TX_BUF_ID is the ID of the first available MB. Other
than that, it should work I believe.
OTOH, since this loop is more like a memset(...0...), wouldn't it be nice to
just clear all MB's CODE registers and then initialize TX_BUF (and others)
afterwards?
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2014-09-03 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 15:03 RFC [PATCH v2 1/2] can: flexcan: fix mailbox initialization Marc Kleine-Budde
2014-09-02 15:03 ` RFC: [PATCH v2 1/2] can: flexcan: Correctly initialize mailboxes Marc Kleine-Budde
2014-09-03 6:58 ` David Jander [this message]
2014-09-03 9:18 ` Marc Kleine-Budde
2014-09-03 14:34 ` David Jander
2014-09-03 14:36 ` Marc Kleine-Budde
2014-09-02 15:03 ` RFC: [PATCH v2 2/2] can: flexcan: increase FLEXCAN_MCR_MAXMB() macro to 7 bits Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140903085856.3a7e1e9a@archvile \
--to=david@protonic.nl \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).