mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	wg@grandegger.com
Cc: kernel@martin.sperl.org, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Add Microchip MCP25XXFD CAN driver
Date: Fri, 12 Jun 2020 13:27:30 +0200	[thread overview]
Message-ID: <690da22a-0cba-43c1-7a29-fac5bc696ce4@pengutronix.de> (raw)
In-Reply-To: <ed3f66c0-28e5-9bfc-729b-457d564638f9@pengutronix.de>

On 6/11/20 10:30 PM, Marc Kleine-Budde wrote:
> On 6/11/20 6:26 PM, Marc Kleine-Budde wrote:
>> I initially started looking at Martin's driver and it was not using several
>> modern CAN driver infrastructures. I then posted some cleanup patches but Martin
>> was not working on the driver any more. Then I decided to rewrite the driver,
>> that is the one I'm hoping to mainline soon.
> 
> Seems the driver still suffers from the same problems the last time I looked at it:
> 
> I'm on a raspi4 with a mcp2518fd connected to spi0 cs0 and cs1.
> 
> Running a canfdtest -vg can0; canfdtest -v can1. It  runs into this problem on a
> unloaded system and scaling_governor=performance  within minutes:
> 
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: Something is wrong - we got a TEF interrupt but we were not able to detect a finished fifo
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: Something is wrong - we got a TEF interrupt but we were not able to detect a finished fifo
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: tefif: fifo 6 not pending - tef data: id: 00000078 flags: 00000c08, ts: 0addbed3 - this may be a problem with spi signal quality- try reducing spi-clock speed if this can get reproduced
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: tefif: fifo 7 not pending - tef data: id: 00000078 flags: 00000e08, ts: 0addc2e5 - this may be a problem with spi signal quality- try reducing spi-clock speed if this can get reproduced
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: tefif: fifo 1 not pending - tef data: id: 00000078 flags: 00000208, ts: 0addc701 - this may be a problem with spi signal quality- try reducing spi-clock speed if this can get reproduced
>> Jun 11 21:27:08 rpi4 kernel: mcp25xxfd spi0.0 can1: tefif: fifo 2 not pending - tef data: id: 00000078 flags: 00000408, ts: 0addcb1b - this may be a problem with spi signal quality- try reducing spi-clock speed if this can get reproduced

Further two mcp2517 on the rpi4, unloaded system, performance dovernor running
cansequence -v can0 -p; cansequence can1 -v; gives:

> Jun 12 12:17:53 rpi4 kernel: mcp25xxfd spi1.0: ECC single bit error at 800
> Jun 12 12:17:53 rpi4 kernel: mcp25xxfd spi1.0: ECC single bit error at 800
> Jun 12 12:17:54 rpi4 kernel: mcp25xxfd spi1.0: ECC double bit error at 800
> Jun 12 12:17:54 rpi4 kernel: mcp25xxfd spi1.0: unidentified system interrupt - intf =  b91a1118
> Jun 12 12:17:54 rpi4 kernel: mcp25xxfd spi1.0: ECC double bit error at 800

I don't see these problems with my driver.

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 |

  reply	other threads:[~2020-06-12 11:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  7:44 Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 1/6] dt-bindings: can: Document devicetree bindings for MCP25XXFD Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 2/6] can: mcp25xxfd: Add Microchip MCP25XXFD CAN-FD driver infrastructure Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 3/6] can: mcp25xxfd: Add support for CAN reception Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 4/6] can: mcp25xxfd: Add CAN transmission support Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 5/6] can: mcp25xxfd: Optimize TEF read by avoiding unnecessary SPI transfers Manivannan Sadhasivam
2020-06-10  7:44 ` [PATCH 6/6] MAINTAINERS: Add entry for Microchip MCP25XXFD CAN network driver Manivannan Sadhasivam
2020-06-11 16:26 ` [PATCH 0/6] Add Microchip MCP25XXFD CAN driver Marc Kleine-Budde
2020-06-11 20:30   ` Marc Kleine-Budde
2020-06-12 11:27     ` Marc Kleine-Budde [this message]
2020-06-17 16:59   ` Kurt Van Dijck
2020-06-17 22:36     ` Marc Kleine-Budde
2020-06-18 12:30       ` Kurt Van Dijck
2020-06-18 12:35         ` Marc Kleine-Budde
2020-06-22 10:25           ` Kurt Van Dijck
2020-06-22 10:55             ` Marc Kleine-Budde
2020-06-22 12:30               ` Kurt Van Dijck
2020-06-22 12:43                 ` Kurt Van Dijck
2020-06-22 12:54                   ` Marc Kleine-Budde
2020-06-22 13:26                     ` Kurt Van Dijck
2020-06-22 13:41                       ` Marc Kleine-Budde
2020-06-18  8:55   ` Manivannan Sadhasivam
2020-06-20  2:43     ` Manivannan Sadhasivam
2020-06-22 11:47     ` Marc Kleine-Budde
2020-06-18 12:06   ` Manivannan Sadhasivam
2020-06-22 11:41     ` 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=690da22a-0cba-43c1-7a29-fac5bc696ce4@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=kernel@martin.sperl.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=wg@grandegger.com \
    /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

all inboxes | Powered by JetHome®