From: Wolfgang Grandegger <wg@grandegger.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Richard Andrysek <richard.andrysek@rg-mechatronics.com>,
linux-can@vger.kernel.org
Subject: Re: arbitration lost error reporting
Date: Fri, 06 Dec 2013 18:59:30 +0100 [thread overview]
Message-ID: <52A21082.9010102@grandegger.com> (raw)
In-Reply-To: <52A1BCEE.5070101@hartkopp.net>
On 12/06/2013 01:02 PM, Oliver Hartkopp wrote:
>
>
> On 06.12.2013 12:45, Marc Kleine-Budde wrote:
>> On 12/06/2013 11:57 AM, Richard Andrysek wrote:
>>>> You can send a diff, to illustrate your changes.
>>>
>>> $ diff /cygdrive/X/bug1/sja1000.c /cygdrive/X/modified_sja1000.c
>>
>> "diff -u" is preferred, but no need to resend it.
>>
>>>>> But I prefare to make some kind of "ioctl" support for that. There are
>>>>> applications, where it shall not happend. Concurrently I've played with
>>>>> taskset and priorities.
>>>>
>>>> ioctl() is not a option here, but there are two options:
>>>> 1) We can put the arbitration lost error to the bus errors,
>>>> but I think that's wrong.
>>>> 2) You can add another ctrlmode to disable arbitration lost error
>>>> reporting.
>>
>>> As Wolgang mentioned it has nothing to do with the patch v6.
>>> Enabling/diabling IRQs is a new feature. So I don't know, if here it is a
>>> right place to continue about that.
>>
>> Yes, why not? :)
>> As I outlined above you have two options. I prefer option 2 and it has a
>> big change of going mainline. The implementation is similar to
>> CAN_CTRLMODE_BERR_REPORTING, just look for it in the kernel source tree
>> and add a new define for arbitration lost error reporting.
>>
>> Do you have a preferred name for the define?
>> - CAN_CTRLMODE_AERR_REPORTING
>> - CAN_CTRLMODE_ARBITRATIONERR_REPORTING to
>
> Loosing the arbitration is not an error. It just can happen from time to time.
Well, if it does not happen often, why do we want to suppress reporting
this error? I still do not see what it's good for.
Wolfgang.
next prev parent reply other threads:[~2013-12-06 17:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 23:03 [PATCH v6] can: sja1000: fix {pre,post}_irq() handling and IRQ handler return value Marc Kleine-Budde
2013-11-25 8:54 ` Marc Kleine-Budde
2013-11-25 18:12 ` Oliver Hartkopp
2013-11-25 22:05 ` Austin Schuh
2013-12-09 19:48 ` Austin Schuh
2013-12-09 21:07 ` Marc Kleine-Budde
2013-12-09 23:50 ` Austin Schuh
2013-12-05 15:50 ` Richard Andrysek
2013-12-05 17:50 ` Wolfgang Grandegger
2013-12-05 19:37 ` Richard Andrysek
2013-12-05 20:26 ` Wolfgang Grandegger
2013-12-06 9:27 ` Richard Andrysek
2013-12-06 9:56 ` Wolfgang Grandegger
2013-12-06 10:32 ` Richard Andrysek
2013-12-06 18:32 ` Wolfgang Grandegger
2013-12-09 9:29 ` Richard Andrysek
2013-12-06 10:12 ` Marc Kleine-Budde
2013-12-06 10:57 ` Richard Andrysek
2013-12-06 11:45 ` arbitration lost error reporting (was: Re: [PATCH v6] can: sja1000: fix {pre,post}_irq() handling and IRQ handler return value) Marc Kleine-Budde
2013-12-06 12:02 ` arbitration lost error reporting Oliver Hartkopp
2013-12-06 12:16 ` Marc Kleine-Budde
2013-12-06 13:21 ` Richard Andrysek
2013-12-06 13:23 ` Marc Kleine-Budde
2013-12-06 17:59 ` Wolfgang Grandegger [this message]
2013-12-07 13:13 ` Oliver Hartkopp
2013-12-09 9:01 ` Richard Andrysek
2013-12-09 10:32 ` 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=52A21082.9010102@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=richard.andrysek@rg-mechatronics.com \
--cc=socketcan@hartkopp.net \
/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.