From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pascal GREGIS <pgs@synerway.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ata_sff_drain_fifo
Date: Wed, 18 Aug 2010 12:44:12 +0100 [thread overview]
Message-ID: <20100818124412.4652eaea@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100818094313.GA3333@gaiman.synerway.com>
> so I guess when status is 0xD0, ATA_DRQ is not set but ATA_BUSY is.
> It would explain why in my case it doesn't drain anything before trying to reset.
>
> Would it be of any interest to drain the fifo also when the ATA_BUSY flag is on, not only the ATA_DRQ ?
If the drive has the busy flag set it is busy, all we can do is wait for
it and if that fails try to reset it. The FIFO drain handles a specific
case where the two ends disagree about the amount of data expected, and
often lets us avoid a reset.
Alan
next prev parent reply other threads:[~2010-08-18 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 9:43 ata_sff_drain_fifo Pascal GREGIS
2010-08-18 11:44 ` Alan Cox [this message]
2010-08-18 16:23 ` ata_sff_drain_fifo Pascal GREGIS
2010-08-18 17:31 ` ata_sff_drain_fifo 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=20100818124412.4652eaea@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pgs@synerway.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