From: Tejun Heo <htejun@gmail.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org, jeremy@sgi.com, liml@rtr.ca
Subject: Re: sata_vsc with iq3124h regression in 2.6.20
Date: Sun, 11 Feb 2007 19:19:32 -0800 [thread overview]
Message-ID: <45CFDCC4.6050400@gmail.com> (raw)
In-Reply-To: <1171063609.29541.6.camel@dwillia2-linux.ch.intel.com>
Dan Williams wrote:
> The error interrupt handling code is still in there and is working. The
> following patch works for me.
>
> ---
> sata_vsc: handle unexpected interrupts when executing a polled IDENTIFY
>
> From: Dan Williams <dan.j.williams@intel.com>
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
>
> drivers/ata/sata_vsc.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/ata/sata_vsc.c b/drivers/ata/sata_vsc.c
> index 0fa1b89..7425d62 100644
> --- a/drivers/ata/sata_vsc.c
> +++ b/drivers/ata/sata_vsc.c
> @@ -258,7 +258,9 @@ static irqreturn_t vsc_sata_interrupt (int irq, void *dev_instance)
> /* Clear interrupt status */
> ata_chk_status(ap);
> handled++;
> - }
> + } else if (qc->tf.command == ATA_CMD_ID_ATA)
> + /* 31244 interrupts on polled IDENTIFY commands */
> + ata_chk_status(ap);
> }
> }
> }
I see. Can you please...
1. move per-port interrupt handling code (everything inside the for
loop) to a separate function
2. make the if/else control block look like the following?
if (unlikely(no irq))
return 0;
if (intr command in progress)
return ata_host_intr()
if (error_intr())
error intr handling sans irq clearing.
clear IRQ
return 1;
3. Post the patch (probably two patches, one to separate out
vsc_port_intr() and another to fix the problem) with proper subject lines.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-02-12 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 23:26 sata_vsc with iq3124h regression in 2.6.20 Dan Williams
2007-02-12 3:19 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 22:21 Williams, Dan J
2007-02-09 22:33 ` Jeff Garzik
2007-02-10 14:58 ` Tejun Heo
2007-02-10 21:08 ` Mark Lord
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=45CFDCC4.6050400@gmail.com \
--to=htejun@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=jeff@garzik.org \
--cc=jeremy@sgi.com \
--cc=liml@rtr.ca \
--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).