From: Steffen Rose <ro@emtas.de>
To: linux-can@vger.kernel.org
Subject: Re: flexcan napi poll and error frames
Date: Fri, 24 Oct 2014 18:36:53 +0200 [thread overview]
Message-ID: <4764001.1dH8LXDQX4@lisa> (raw)
In-Reply-To: <544A78A8.40909@marel.com>
Hello,
Am Freitag, 24. Oktober 2014, 16:04:56 schrieben Sie:
> > We can do little if the CAN controller does not notify the Software
> >> via interrupt.
> > Yes, that's why I wanted to figure out if it's a controller problem or
> > not.
> > Turns out it's a controller problem, but perhaps we can work around it?
> > E.g. if we check esr for state changes every time someone transmits a
> > frame, both of these problems would go away. Would it be unacceptable
> > overhead to do so?
>
> I've just confirmed that this "fix" works, but only if berr-reporting is
> enabled.
Is this workaround working in case of an open CAN Bus?
(Ack error situation)
The flexcan can generate an error interrupt after every CAN bus error. But in
case of an error situation the interrupt load would be very high (e.g. short
circuit of the CAN).
--
Mit freundlichen Grüßen
Steffen Rose
www.emtas.de
next prev parent reply other threads:[~2014-10-24 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 10:26 flexcan napi poll and error frames Andri Yngvason
2014-10-24 10:43 ` Wolfgang Grandegger
2014-10-24 10:55 ` Andri Yngvason
2014-10-24 12:33 ` Wolfgang Grandegger
2014-10-24 14:39 ` Andri Yngvason
2014-10-24 16:04 ` Andri Yngvason
2014-10-24 16:36 ` Steffen Rose [this message]
2014-10-24 17:40 ` Andri Yngvason
2014-10-27 7:29 ` David Jander
[not found] ` <544E2C19.1050608@marel.com>
2014-10-27 14:01 ` David Jander
2014-10-27 15:53 ` Andri Yngvason
2014-10-24 19:08 ` 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=4764001.1dH8LXDQX4@lisa \
--to=ro@emtas.de \
--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).