From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Jason R1 White <White_Jason_R1@cat.com>
Cc: linux-can@vger.kernel.org
Subject: Re: FlexCAN on i.MX28 interrupt flooding retrying send
Date: Fri, 07 Mar 2014 15:40:26 +0100 [thread overview]
Message-ID: <5319DA5A.7080003@pengutronix.de> (raw)
In-Reply-To: <OFA84C0F6D.092C777B-ON86257C94.004E3F0B-86257C94.004F1F2D@notes.cat.com>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On 03/07/2014 03:24 PM, Jason R1 White wrote:
> Marc,
>
> What do you mean that flexcan driver doesn't have the improvement for the
> mx28? What do you mean by non DT? I see e358784 in the kernel tree, but
Your flexcan driver does always enable bus errors, because on most older
socks you need the bus errors as a workaround to detect the warning and
passive interrupt. With modern kernel on the mx28, the bus error is not
enabled by default.
In the development of the kernel, the mx28 was first switched to Device
Tree (DT) only, then we figured out, that the mx28 doesn't have the
above mentioned problem and the bus error is disabled by default.
> we are not yet picking it up. Is there any other fixes for the mx28 that
> you are aware of? Can you send the patch set for the berror_limit? We
> experienced a lot of issues with the error interrupt causing a lot of
> cpu usage and ended up having to disable it. Normally I like to at
> least detect the bus error condition.
I'm in the hot phase of two projects, so it will take some time to dig
into the berr_limit again, as it needs some work.
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: 242 bytes --]
next prev parent reply other threads:[~2014-03-07 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 8:08 FlexCAN on i.MX28 interrupt flooding retrying send Stanislav Meduna
2014-03-07 8:16 ` Marc Kleine-Budde
2014-03-07 8:40 ` Wolfgang Grandegger
[not found] ` <OF203965D8.128520F3-ON86257C94.004FA84A-86257C94.0050AF36@notes.cat.com>
2014-03-07 15:36 ` Wolfgang Grandegger
2014-03-07 8:32 ` Matthias Klein
2014-03-07 8:46 ` Marc Kleine-Budde
2014-03-07 13:36 ` Stanislav Meduna
2014-03-07 13:54 ` Marc Kleine-Budde
[not found] ` <OFA84C0F6D.092C777B-ON86257C94.004E3F0B-86257C94.004F1F2D@notes.cat.com>
2014-03-07 14:40 ` Marc Kleine-Budde [this message]
2014-03-07 15:55 ` Wolfgang Grandegger
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=5319DA5A.7080003@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=White_Jason_R1@cat.com \
--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 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).