From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Gianluca <gmattiroli@midsx.ch>
Cc: linux-can@vger.kernel.org
Subject: Re: socketCAN mcp2515 - rx buffer overflow
Date: Thu, 08 Mar 2012 15:11:15 +0100 [thread overview]
Message-ID: <4F58BE03.5030905@pengutronix.de> (raw)
In-Reply-To: <loom.20120308T140608-84@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On 03/08/2012 02:09 PM, Gianluca wrote:
> Hi All,
> I'm using an embedded Armadeus evaluation board - apf51 - with the mcp2515 CAN
> controller (via spi) and linux 2.6.38.8.
Using an SPI attached CAN controller is a really bad choice. Try is
upgrading to mx53, which has as far as I know one or even two internal
flexcan cores, an option for you? Another option is to attach a local
bus capable controller like the SJA1000 to your CPU, or use an USB
dongle or a PCMCIA card.
The next thing is the SPI driver on the (mainline) mx51. If I remember
correctly the mainline kernel doesn't support DMA for the SPI driver
yet. I don't know if the freescale kernel does. Depending on your kernel
version there are some knobs to tune the PIO SPI driver, mainly to
increase the priority of the SPI task.
Last but not least, there is a not yet mainlined improved version of the
mcp2515 driver around.
regards, 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 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-03-08 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:09 socketCAN mcp2515 - rx buffer overflow Gianluca
2012-03-08 14:11 ` Marc Kleine-Budde [this message]
2012-03-08 14:35 ` Gianluca
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=4F58BE03.5030905@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=gmattiroli@midsx.ch \
--cc=linux-can@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.