From: Tom Evans <tom_usenet@optusnet.com.au>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Viktor Babrian <babrian.viktor@renyi.mta.hu>,
Andri Yngvason <andri.yngvason@marel.com>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH 3.19-rc3] c_can: SIE disabled when berr-reporting is off to reduce irq flood
Date: Tue, 20 Jan 2015 09:35:56 +1100 [thread overview]
Message-ID: <54BD86CC.70302@optusnet.com.au> (raw)
In-Reply-To: <54BBFCAF.2090603@pengutronix.de>
On 19/01/15 05:34, Marc Kleine-Budde wrote:
> On 01/18/2015 07:30 PM, Viktor Babrian wrote:
>>
>> Status interrupt is to be disabled if bus error reporting is off in order
>> to reduce interrupt flood when e.g. a frame is not acked. Side effect is
>> that when berr-reporting off, warn->pass and pass-warn state transitions
>> may be reported later (upon a successful rx/tx event) or even go
>> undetected. With proper implementation, these transitions could always be
>> detected (but still later). It is considered better to have a non-accurate
>> report of these transitions than having a non-responding system in
>> possible scenarios.
>>
>> Signed-off-by: Viktor Babrian <babrian.viktor@renyi.mta.hu>
>
> NACK. The transitions are important for some applications. I've an not
> yet mainlined series that limits the bus errors. I'm going to port them
> to the current kernel tomorrow. Can you test it?
Those "some applications" can enable "CAN_CTRLMODE_BERR_REPORTING" and get
error reporting and prompt (and complete) state reporting.
Doesn't that answer your concern?
That approach was implemented in flexcan.c as per this patch:
> Author: Wolfgang Grandegger <wg@grandegger.com> 2012-10-11 06:10:42
> Committer: Marc Kleine-Budde <mkl@pengutronix.de> 2012-10-24 03:43:17
can: flexcan: disable bus error interrupts for the i.MX6q
This patch adds some Flexcan version info and removes the feature flag
FLEXCAN_HAS_BROKEN_ERR_STATE for the i.MX6Q. It also has the line
[TR]WRN_INT properly connected.
You approved this approach then (although possibly not knowing that that was
what the patch was doing then).
Tom Evans
next prev parent reply other threads:[~2015-01-19 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 17:54 [PATCH v5 3/5] can: mscan: Consolidate and unify state change handling Andri Yngvason
2015-01-12 17:18 ` c_can: (newbie) high system load when frame not acked? Viktor Babrian
[not found] ` <1735533.0yOonAfCy1@heinz>
2015-01-12 18:50 ` Viktor Babrian
2015-01-13 1:19 ` Tom Evans
2015-01-13 15:10 ` Viktor Babrian
2015-01-13 15:16 ` Marc Kleine-Budde
2015-01-13 15:54 ` Viktor Babrian
2015-01-13 15:55 ` Marc Kleine-Budde
2015-01-13 15:32 ` Andri Yngvason
2015-01-14 1:35 ` Tom Evans
2015-01-14 9:55 ` Andri Yngvason
2015-01-15 0:29 ` Tom Evans
2015-01-18 18:30 ` [PATCH 3.19-rc3] c_can: SIE disabled when berr-reporting is off to reduce irq flood Viktor Babrian
2015-01-18 18:34 ` Marc Kleine-Budde
2015-01-18 18:52 ` Viktor Babrian
2015-01-18 18:56 ` Marc Kleine-Budde
2015-01-19 11:32 ` Viktor Babrian
2015-01-19 22:35 ` Tom Evans [this message]
2015-01-18 19:01 ` [PATCH 3.19-rc3] c_can: end transmission on network stop Viktor Babrian
2015-01-20 14:39 ` 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=54BD86CC.70302@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=andri.yngvason@marel.com \
--cc=babrian.viktor@renyi.mta.hu \
--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;
as well as URLs for NNTP newsgroup(s).