linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: 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 12:16:31 +0100	[thread overview]
Message-ID: <4F34FC8F.4000104@pengutronix.de> (raw)
In-Reply-To: <4F34F8BC.3030903@peak-system.com>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

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...

Is 0xff a valid value for REG_SR in the first place? If not we can for
example exit the interrupt handler.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-02-10 11:16 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 [this message]
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

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=4F34FC8F.4000104@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --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 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).