From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: Stephane Grosjean <s.grosjean@peak-system.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: [PATCH v3] can/sja1000: add support for PEAK-System PCMCIA card
Date: Wed, 15 Feb 2012 20:46:06 +0100 [thread overview]
Message-ID: <4F3C0B7E.1060806@hartkopp.net> (raw)
In-Reply-To: <4F3BC9DB.6040604@grandegger.com>
>> I would also have say that before, but I checked that IRQ_NONE may be
>> processed as spurious, so I don't even know, for the moment. LDD3
>> chapter 10 also says:
>>
>>> Interrupt handlers should return a value indicating whether there was
>>> actually an
>>> interrupt to handle. If the handler found that its device did, indeed,
>>> need attention, it
>>> should return IRQ_HANDLED; otherwise the return value should be IRQ_NONE.
>>
>> So, what does this "need attention" stands for? Since the device is
>> unplugged, we could say that it didn't need any attention anymore...
>> But, on the other hand, the ems_pcmcia driver does return IRQ_HANDLED
>> when its private check fails to detect the card and it has been
>> approved, so, where is the truth? Near the perfection? ;-)
>
> From http://lxr.linux.no/#linux+v3.2.6/include/linux/irqreturn.h:
>
> IRQ_NONE interrupt was not from this device
See:
http://lxr.linux.no/#linux+v3.2.6/kernel/irq/spurious.c#L178
I think at plug-out we get very little IRQ_NONE return values that should be
ok not to damage the entire handling of that specific irq line ...
Regards,
Oliver
next prev parent reply other threads:[~2012-02-15 19:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 15:56 [PATCH v3] can/sja1000: add support for PEAK-System PCMCIA card Stephane Grosjean
2012-02-13 9:14 ` Marc Kleine-Budde
2012-02-13 10:01 ` Stephane Grosjean
2012-02-13 10:14 ` Wolfgang Grandegger
2012-02-13 10:41 ` Oliver Hartkopp
2012-02-13 11:02 ` Wolfgang Grandegger
2012-02-13 11:06 ` Marc Kleine-Budde
2012-02-13 11:08 ` Wolfgang Grandegger
2012-02-13 19:55 ` Oliver Hartkopp
2012-02-13 20:23 ` Wolfgang Grandegger
2012-02-14 9:14 ` Stephane Grosjean
2012-02-14 9:30 ` Wolfgang Grandegger
2012-02-14 9:59 ` Oliver Hartkopp
2012-02-14 10:16 ` Stephane Grosjean
2012-02-14 16:41 ` Oliver Hartkopp
2012-02-15 7:03 ` Wolfgang Grandegger
2012-02-15 8:05 ` Oliver Hartkopp
2012-02-15 8:37 ` Wolfgang Grandegger
2012-02-15 19:32 ` Oliver Hartkopp
2012-02-15 11:52 ` Stephane Grosjean
2012-02-15 15:06 ` Wolfgang Grandegger
2012-02-15 16:00 ` Stephane Grosjean
2012-02-15 19:46 ` Oliver Hartkopp [this message]
2012-02-13 10:46 ` Stephane Grosjean
2012-02-13 10:56 ` 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=4F3C0B7E.1060806@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.grosjean@peak-system.com \
--cc=wg@grandegger.com \
/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).