From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs
Date: Fri, 21 Nov 2008 19:59:51 +0300 [thread overview]
Message-ID: <4926E907.20706@ru.mvista.com> (raw)
In-Reply-To: <49263552.8090602@kernel.org>
Hello.
Tejun Heo wrote:
> The DMA_IRQ bit in the bmdma status register is always set when IDEIRQ
> is asserted allowing spurious IRQ detection. Detect spurious IRQs and
> clear them. This protects ata_piix against nobody-cared which gets
> reported not so rarely.
This should be more generic, as several IDE controllers have the separate
IDE interrupt status bits.
> Signed-off-by: Tejun Heo <tj@kernel.org>
> diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
> index 8e37be1..b438edc 100644
> --- a/drivers/ata/ata_piix.c
> +++ b/drivers/ata/ata_piix.c
> @@ -922,6 +922,58 @@ static int piix_sidpr_scr_read(struct ata_link *link,
> return 0;
> }
>
> +static irqreturn_t piix_interrupt(int irq, void *dev_instance)
> +{
[...]
> + /*
> + * Control reaches here if HSM is not expecting IRQ.
> + * If the controller is actually asserting IRQ line,
> + * this will lead to nobody cared. Fortuantely,
> + * DMA_INTR of PIIX is set whenever IDEIRQ is set so
Frankly speaking, I'm not sure about the PIIX chips themselves... Is that
documented by Intel?
MBR, Sergei
next prev parent reply other threads:[~2008-11-21 16:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 4:13 [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs Tejun Heo
2008-11-21 10:25 ` Alan Cox
2008-11-21 13:07 ` Tejun Heo
2008-11-25 17:07 ` Jeff Garzik
2008-11-26 2:52 ` Tejun Heo
2008-11-26 10:47 ` Alan Cox
2008-11-26 12:26 ` Sergei Shtylyov
2008-11-26 12:28 ` Sergei Shtylyov
2008-11-26 12:37 ` Sergei Shtylyov
2008-11-26 17:34 ` Jeff Garzik
2008-11-26 17:45 ` Tejun Heo
2008-11-26 18:40 ` Alan Cox
2008-11-26 18:57 ` Tejun Heo
2008-11-28 2:31 ` Tejun Heo
2008-12-04 16:33 ` Mark Lord
2008-12-04 16:35 ` Alan Cox
2008-11-21 16:59 ` Sergei Shtylyov [this message]
2008-11-21 17:05 ` Tejun Heo
2008-11-25 17:08 ` Jeff Garzik
2008-11-25 17:15 ` Alan Cox
2008-11-26 2:45 ` Tejun Heo
2008-11-26 10:33 ` Alan Cox
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=4926E907.20706@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/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).