From: Tejun Heo <htejun@gmail.com>
To: Edward Falk <efalk@google.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: Re: [PATCH linux-2.6.13-rc3] SATA: rewritten sil24 driver
Date: Thu, 4 Aug 2005 11:20:25 +0900 [thread overview]
Message-ID: <20050804022025.GA19237@htj.dyndns.org> (raw)
In-Reply-To: <20050803142812.GA25446@htj.dyndns.org>
Hello, Edward.
One more question.
> > >
> > >I think this will work (adapted from sil_interrupt():
> > >
> > >static void sil_irq_clear(struct ata_port *ap)
> > >{
> > > struct sil_port_priv *pp = ap->private_data;
> > > struct Port_Registers *port_base = pp->pregs;
> > > unsigned long port_int;
> > >
> > > port_int = readl((void *)&port_base->IntStatus);
> > > writel(port_int, &port_base->IntStatus);
> > >}
> > >
> > >I'm assuming that this entry point is expected to clear all interrupts, no?
> >
> > Correct.
> >
>
> I'll verify with the error register clearing part of the original
> driver and submit a patch.
>
Command completion interrupt is automatcally cleared by reading
PORT_SLOT_STAT register (SlotStatus in the original driver), and error
registers should be manually cleared by writing to PORT_IRQ_STAT
(IntStatus).
I agree that above code should clear both. Just wanna verify. Have
you tested it and/or do you have any information confirming this? If
we don't have any further info, I think we should read PORT_SLOT_STAT
before clearing PORT_IRQ_STAT to be on the safe side.
Thanks.
--
tejun
next prev parent reply other threads:[~2005-08-04 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050728013622.GA14026@htj.dyndns.org>
2005-07-28 20:27 ` Jeff Garzik
2005-07-30 8:17 ` Tejun Heo
2005-08-02 22:56 ` Edward Falk
2005-08-03 4:09 ` Jeff Garzik
2005-08-03 14:28 ` Tejun Heo
2005-08-04 2:20 ` Tejun Heo [this message]
2005-08-04 18:46 ` Edward Falk
2005-08-04 8:51 ` Tejun Heo
2005-08-08 17:31 Carlos Pardo
2005-08-08 17:37 ` Jeff Garzik
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=20050804022025.GA19237@htj.dyndns.org \
--to=htejun@gmail.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=efalk@google.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®