From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
mark.paulus@technologist.com, sveint@gmail.com,
bug-track@fisher-privat.net
Subject: Re: [PATCH #upstream-fixes] libata: clear link->eh_info.serror from ata_std_postreset()
Date: Fri, 07 Dec 2007 18:53:29 -0500 [thread overview]
Message-ID: <4759DCF9.10407@garzik.org> (raw)
In-Reply-To: <4759DB75.1010702@gmail.com>
Tejun Heo wrote:
> link->eh_info.serror is used to cache SError for controllers which
> need it cleared from interrupt handler to clear IRQ. It also should
> be cleared after reset just like SError itself.
>
> Make ata_std_postreset() clear link->eh_info.serror too and update
> sata_sil such that it doesn't care about bookkeeping the value.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-core.c | 1 +
> drivers/ata/sata_sil.c | 11 +----------
> 2 files changed, 2 insertions(+), 10 deletions(-)
>
> Index: work/drivers/ata/libata-core.c
> ===================================================================
> --- work.orig/drivers/ata/libata-core.c
> +++ work/drivers/ata/libata-core.c
> @@ -3923,6 +3923,7 @@ void ata_std_postreset(struct ata_link *
> /* clear SError */
> if (sata_scr_read(link, SCR_ERROR, &serror) == 0)
> sata_scr_write(link, SCR_ERROR, serror);
> + link->eh_info.serror = 0;
IMO it would make more sense to record the state of the hardware
following sata_scr_write() than simply zeroing the cache value.
Just a gut feeling... it seems like having a manufactured value (zero)
rather than the last known from-the-hardware value could lead to
inconsistencies.
Comments?
Jeff
next prev parent reply other threads:[~2007-12-07 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 23:45 [PATCH #upstream-fixes] sata_sil: fix spurious IRQ handling Tejun Heo
2007-12-07 23:47 ` [PATCH #upstream-fixes] libata: clear link->eh_info.serror from ata_std_postreset() Tejun Heo
2007-12-07 23:53 ` Jeff Garzik [this message]
2007-12-08 0:05 ` Tejun Heo
2007-12-18 1:37 ` Jeff Garzik
2007-12-18 1:37 ` [PATCH #upstream-fixes] sata_sil: fix spurious IRQ handling 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=4759DCF9.10407@garzik.org \
--to=jeff@garzik.org \
--cc=bug-track@fisher-privat.net \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mark.paulus@technologist.com \
--cc=sveint@gmail.com \
/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).