Linux CAN drivers development
 help / color / mirror / Atom feed
From: Benoît <benoit@pouic.eu>
To: linux-can@vger.kernel.org
Cc: Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH] can: mcp251x: avoid repeated frame bug
Date: Mon, 03 Sep 2012 19:13:51 +0200	[thread overview]
Message-ID: <5044E54F.7020507@pouic.eu> (raw)
In-Reply-To: <1346674649-10181-1-git-send-email-mkl@pengutronix.de>

Hello Marc,

First, thank you for your attention on this bug.

On 09/03/2012 02:17 PM, Marc Kleine-Budde wrote:

> From: Benoit <benoit@pouic.eu>
>
> The MCP2515 has a silicon bug causing repeated frame transmission, see section
> 5 of MCP2515 Rev. B Silicon Errata Revision G (March 2007).
>
> Basically, setting TXBnCTRL.TXREQ in either SPI mode (00 or 11) will eventually
> cause the bug. The workaround proposed by Microchip is to use mode 00 and send
> an RTS command on the SPI bus to initiate the transmission.
>
> TODO: get S-o-b from Benoit <benoit@pouic.eu>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> Hello Benoit,
>
> can you please test this patch, if it still fixes your problem. In order to
> integrate this patch into the kernel, I need you Signed-off-by [1] with you
> real name.

I just carefully ran some before/after tests with your updated patch and I confirm the problem is still fixed with it.

As for my "Signed-off-by", here it goes:

Signed-off-by: Benoît Locher <Benoit.Locher@skf.com>

By the way, about using spi_write()instead of mcp251x_spi_trans(): I innocently thought it would make less function call nesting,
trying to improve response time of the driver particularly on my Raspberry Pi.

Best Regards,

Benoît.

>
> regards, Marc
>
> [1] http://lxr.free-electrons.com/source/Documentation/SubmittingPatches#L298
>
>   drivers/net/can/mcp251x.c |   11 ++++++++++-
>   1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/mcp251x.c b/drivers/net/can/mcp251x.c
> index a580db2..26e7129 100644
> --- a/drivers/net/can/mcp251x.c
> +++ b/drivers/net/can/mcp251x.c
> @@ -83,6 +83,11 @@
>   #define INSTRUCTION_LOAD_TXB(n)	(0x40 + 2 * (n))
>   #define INSTRUCTION_READ_RXB(n)	(((n) == 0) ? 0x90 : 0x94)
>   #define INSTRUCTION_RESET	0xC0
> +#define RTS_TXB0		0x01
> +#define RTS_TXB1		0x02
> +#define RTS_TXB2		0x04
> +#define INSTRUCTION_RTS(n)	(0x80 | ((n) & 0x07))
> +
>   
>   /* MPC251x registers */
>   #define CANSTAT	      0x0e
> @@ -397,6 +402,7 @@ static void mcp251x_hw_tx_frame(struct spi_device *spi, u8 *buf,
>   static void mcp251x_hw_tx(struct spi_device *spi, struct can_frame *frame,
>   			  int tx_buf_idx)
>   {
> +	struct mcp251x_priv *priv = dev_get_drvdata(&spi->dev);
>   	u32 sid, eid, exide, rtr;
>   	u8 buf[SPI_TRANSFER_BUF_LEN];
>   
> @@ -418,7 +424,10 @@ static void mcp251x_hw_tx(struct spi_device *spi, struct can_frame *frame,
>   	buf[TXBDLC_OFF] = (rtr << DLC_RTR_SHIFT) | frame->can_dlc;
>   	memcpy(buf + TXBDAT_OFF, frame->data, frame->can_dlc);
>   	mcp251x_hw_tx_frame(spi, buf, frame->can_dlc, tx_buf_idx);
> -	mcp251x_write_reg(spi, TXBCTRL(tx_buf_idx), TXBCTRL_TXREQ);
> +
> +	/* use INSTRUCTION_RTS, to avoid "repeated frame problem" */
> +	priv->spi_tx_buf[0] = INSTRUCTION_RTS(1 << tx_buf_idx);
> +	mcp251x_spi_trans(priv->spi, 1);
>   }
>   
>   static void mcp251x_hw_rx_frame(struct spi_device *spi, u8 *buf,



  reply	other threads:[~2012-09-03 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 12:17 [PATCH] can: mcp251x: avoid repeated frame bug Marc Kleine-Budde
2012-09-03 17:13 ` Benoît [this message]
2012-09-03 17:59   ` Marc Kleine-Budde
2012-09-03 18:09     ` Benoît
2012-09-05 19:59   ` Marc Kleine-Budde
  -- strict thread matches above, loose matches on Subject: below --
2012-09-04 20:55 pull-request: can 2012-09-04 Marc Kleine-Budde
2012-09-04 20:55 ` [PATCH] can: mcp251x: avoid repeated frame bug 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=5044E54F.7020507@pouic.eu \
    --to=benoit@pouic.eu \
    --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