linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <tj@kernel.org>, 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: Wed, 26 Nov 2008 15:37:29 +0300	[thread overview]
Message-ID: <492D4309.3070006@ru.mvista.com> (raw)
In-Reply-To: <492D40F3.5000506@ru.mvista.com>

Hello, I wrote:

>>> 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)
>>   
> All BMDMA controllers I know about are sata_sil (already has private
>
>   The late chips do have the alternate interrupt latch bits in I/O 
> space (at BMIDE base + 3).

   Just looked into th driver, so to be correct the MRDMODE register is 
at BMIDE base + 1.

MBR, Sergei



  reply	other threads:[~2008-11-26 12:37 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 [this message]
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
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=492D4309.3070006@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).