From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Piggin <npiggin@suse.de>
Cc: jgarzik@redhat.com, linux-ide@vger.kernel.org
Subject: Re: patch "libata-sff: Fix oops for pnp devices with no ctl" causes regression
Date: Thu, 5 Jun 2008 12:19:35 +0100 [thread overview]
Message-ID: <20080605121935.1a1ecb59@core> (raw)
In-Reply-To: <20080605103116.GC11366@wotan.suse.de>
> > @@ -1583,6 +1583,12 @@ inline unsigned int ata_sff_host_intr(struct ata_port *ap
> > if (status & ATA_BUSY)
> > goto idle_irq;
> >
> > + /* check main status, clearing INTRQ */
> > + status = ap->ops->sff_check_status(ap);
> > + if (unlikely(status & ATA_BUSY))
> > + goto idle_irq;
> > +
> > +
Aha all is revealed: and yes it would only show up on a few boxes
libata-sff: Don't assume that check_status is an SFF read
From: Alan Cox <alan@redhat.com>
For a few controllers the sff check status is actually a method not an I/O
access and we must call the method when doing the IRQ check
---
drivers/ata/libata-sff.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Signed-off-by: Alan Cox <alan@redhat.com>
diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c
index 90d20c6..215d186 100644
--- a/drivers/ata/libata-sff.c
+++ b/drivers/ata/libata-sff.c
@@ -278,7 +278,7 @@ static u8 ata_sff_irq_status(struct ata_port *ap)
return status;
}
/* Clear INTRQ latch */
- status = ata_sff_check_status(ap);
+ status = ap->ops->sff_check_status(ap);
return status;
}
prev parent reply other threads:[~2008-06-05 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 5:09 patch "libata-sff: Fix oops for pnp devices with no ctl" causes regression Nick Piggin
2008-06-05 9:24 ` Alan Cox
2008-06-05 10:05 ` Jeff Garzik
2008-06-05 10:21 ` Nick Piggin
2008-06-05 10:31 ` Nick Piggin
2008-06-05 11:19 ` Alan Cox [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=20080605121935.1a1ecb59@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=npiggin@suse.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 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.