From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Stephane Grosjean <s.grosjean@peak-system.com>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: can/sja1000: potential issue in sja1000.c?
Date: Fri, 10 Feb 2012 16:39:24 +0100 [thread overview]
Message-ID: <4F353A2C.10401@hartkopp.net> (raw)
In-Reply-To: <4F34FC8F.4000104@pengutronix.de>
On 10.02.2012 12:16, Marc Kleine-Budde wrote:
> On 02/10/2012 12:00 PM, Stephane Grosjean wrote:
>> Hi all,
>>
>> While always fighting against pcmcia Oliver (very hot) unplug issue, I
>> decided to have a look to the sja1000 lib, since the pcmcia driver ISR
>> does call "sja1000_interrupt()",
>>
>> Unfortunately, I found that:
>>
>> if (isrc & IRQ_RI) {
>> /* receive interrupt */
>> while (status & SR_RBS) {
>> sja1000_rx(dev);
>> status = priv->read_reg(priv, REG_SR);
>> }
>> }
>>
>> My problem is, once the card is unplugged, every ioread in its
>> corresponding io space does return 0xff...
>> I just change this potential infinite while() into a corresponding
>> for(;;) loop to test, like this:
>>
>> - while (status & SR_RBS) {
>> + int i;
>> + for (i = 0; (status & SR_RBS) && (i < 10); i++) {
>>
>> And no more PC hang!
>>
>> Can you confirm this, please?
>>
>> @Oliver: IMHO, the 0xff (invalid) value is also the reason of the
>> "wakeup interrupt" message you got when unplugging the cards from their
>> slots...
Yes. I've also seen that now in the code ... should have looked earlier 8-)
> Is 0xff a valid value for REG_SR in the first place? If not we can for
> example exit the interrupt handler.
The question is, if a RX interrupt can occur, when the sja1000 is in bus-off
state.
The used status register has a bit for bus-off which is "1" in the bus-off
case. Assuming RX interrupts can only occur in a 'bus-on' state, this bit can
be assumed to be '0'.
Therefore checking for 0xFF should make it.
We can check it here
http://lxr.linux.no/#linux+v3.2.5/drivers/net/can/sja1000/sja1000.c#L495
and here
http://lxr.linux.no/#linux+v3.2.5/drivers/net/can/sja1000/sja1000.c#L511
So it could look like this:
diff --git a/drivers/net/can/sja1000/sja1000.c b/drivers/net/can/sja1000/sja1000.c
index ebbcfca..f7526a7 100644
--- a/drivers/net/can/sja1000/sja1000.c
+++ b/drivers/net/can/sja1000/sja1000.c
@@ -493,6 +493,10 @@ irqreturn_t sja1000_interrupt(int irq, void *dev_id)
n++;
status = priv->read_reg(priv, REG_SR);
+ /* check for absent controller due to hw unplug */
+ if (status == 0xFF)
+ break;
+
if (isrc & IRQ_WUI)
netdev_warn(dev, "wakeup interrupt\n");
@@ -504,8 +508,8 @@ irqreturn_t sja1000_interrupt(int irq, void *dev_id)
netif_wake_queue(dev);
}
if (isrc & IRQ_RI) {
- /* receive interrupt */
- while (status & SR_RBS) {
+ /* receive interrupt / check for absent controller */
+ while (status & SR_RBS && status != 0xFF) {
sja1000_rx(dev);
status = priv->read_reg(priv, REG_SR);
}
@Stephane: Can you check that patch? I'm out of hw right now.
Regards,
Oliver
prev parent reply other threads:[~2012-02-10 15:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:12 [PATCH v2] can/sja1000: add support for PEAK-System PCMCIA card Stephane Grosjean
2012-02-03 16:44 ` Oliver Hartkopp
2012-02-06 16:03 ` Oliver Hartkopp
2012-02-06 17:05 ` Sven Geggus
2012-02-06 17:41 ` Oliver Hartkopp
[not found] ` <4F30F691.5070307@peak-system.com>
2012-02-07 13:13 ` About can/usb v4 patches serie Oliver Hartkopp
2012-02-07 13:43 ` Stephane Grosjean
2012-02-07 13:51 ` Oliver Hartkopp
2012-02-15 14:41 ` Stephane Grosjean
2012-02-15 20:05 ` Oliver Hartkopp
2012-02-10 11:00 ` can/sja1000: potential issue in sja1000.c? Stephane Grosjean
2012-02-10 11:16 ` Marc Kleine-Budde
2012-02-10 11:44 ` Wolfgang Grandegger
2012-02-10 15:32 ` Sebastian Haas
2012-02-10 15:37 ` Marc Kleine-Budde
2012-02-10 11:56 ` Wolfgang Grandegger
2012-02-10 15:39 ` Oliver Hartkopp [this message]
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=4F353A2C.10401@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.grosjean@peak-system.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 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.