linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstraem-fixes] ata_piix: detect and clear spurious IRQs
Date: Thu, 27 Nov 2008 02:45:00 +0900	[thread overview]
Message-ID: <492D8B1C.405@kernel.org> (raw)
In-Reply-To: <492D88B9.7040608@garzik.org>

Jeff Garzik wrote:
> Alan Cox wrote:
>>> All BMDMA controllers I know about are sata_sil (already has private
>>> irq handler) and ata_piix (this patch).  Alan, how do other
>>> controllers do it?
>>
>> CMD chipsets do a register read .. from PCI config space (gak)
>> SIL680 is similar
>> SI3112 adds the fact you need to keep at the PHY as well.
>> Promise uses a magic register at dmabase + 0x1D which holds irq bits
>>
>> What I'd like to understand better is why we need any
>> of these ...
> 
> Indeed!

Well, this patch was necessary for a netbook with PATA SSD.  The ATA
implementation of the SSD was quite flaky and under certain
circumstances, during resume SRST, the drive would raise the IRQ line
regardless of NIEN and will stay that way for several seconds, thus
triggering nobody cared.  Other than detecting and clearing the
spurious IRQ, there just isn't much driver can do to work around
problems like this.

Thanks.

-- 
tejun

  reply	other threads:[~2008-11-26 17:45 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 [this message]
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
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=492D8B1C.405@kernel.org \
    --to=tj@kernel.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.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).