From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] sata_sil: update device hotplug handling, take #2
Date: Mon, 12 Jun 2006 09:38:41 -0400 [thread overview]
Message-ID: <448D6E61.1060704@pobox.com> (raw)
In-Reply-To: <20060612094555.GA5751@htj.dyndns.org>
Tejun Heo wrote:
> SIEN on some 3112 controllers doesn't mask SATA IRQ properly. IRQ
> stays asserted even after SIEN is masked and IRQ is acked. Also, even
> while frozen, any SATA PHY event including hardreset raises SATA IRQ.
> Clearing SError seems to be the only way to deassert SATA IRQ.
>
> This patch makes sil_host_intr() clear SError on SATA IRQs and ignore
> SATA IRQs reported while frozen so that hardreset doesn't trigger
> hotplug event (which ends up hardresetting again).
>
> In such cases, the port still gets re-frozen to minimize the danger of
> screaming interrupts. This results in one nil EH repeat on
> controllers with broken SIEN but other than that does no harm.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
> ---
>
> Here's the revised version. The PCMCIA 3112 controller simply cannot
> mask SATA IRQs w/ SIEN. I've tested it w/ discrete 3112 and 3114
> cards and the PCMCIA one. All work fine with this patch applied.
Applied.
Note that it is helpful to read the FreeBSD 311x driver, to see what
error handling they use. It seems like they reset the chip much more
frequently than we do.
Jeff
prev parent reply other threads:[~2006-06-12 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 5:18 [PATCH] sata_sil: update device hotplug handling Tejun Heo
2006-06-12 6:08 ` Jeff Garzik
2006-06-12 7:42 ` Tejun Heo
2006-06-12 9:45 ` [PATCH] sata_sil: update device hotplug handling, take #2 Tejun Heo
2006-06-12 13:38 ` Jeff Garzik [this message]
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=448D6E61.1060704@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--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).