From: Tejun Heo <htejun@gmail.com>
To: Jose Alberto Reguero <jareguero@telefonica.net>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: Add suport for Marvell 88SE6121 in ahci
Date: Sun, 18 Mar 2007 22:48:32 +0900 [thread overview]
Message-ID: <45FD4330.1020108@gmail.com> (raw)
In-Reply-To: <200703181335.41988.jareguero@telefonica.net>
Jose Alberto Reguero wrote:
>> The flag is there primarily for ICH ahci's. Marvell might be different.
>> Care to remove SKIP_D2H_BSY and test a LOT of hotplugging with several
>> different devices? :-)
>
> With SKIP_D2H_BSY I have a old dmesg -> dmesg1 (2.6.20 I think)
> I test with and a external sata disk without SKIP_D2H_BSY -> dmes2
> (2.6.21-rc4)
> Both takes ~8 seconds.
I see. Was the disk spun up when you hotplugged it? The condition
doesn't trigger always and more importantly, there is no way to reliably
wait for the condition in ahci. ahci's TF status register is read from
the received D2H Reg FIS area and there is no mechanism to set the BSY
bit on a PHY event, so no matter what we do in the driver, there is an
inherent race.
ie. we can try to set the BSY bit in the interrupt handler right after a
PHY event but the hardware can always beat us and when that happens we
set BSY after the first D2H Reg FIS is received which will in turn cause
wait timeout, so I'm voting for keeping the flag.
Thanks.
--
tejun
prev parent reply other threads:[~2007-03-18 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 14:04 Add suport for Marvell 88SE6121 in ahci Jose Alberto Reguero
2007-01-31 15:03 ` Jeff Garzik
2007-01-31 16:43 ` Jose Alberto Reguero
2007-03-16 14:21 ` Jose Alberto Reguero
2007-03-18 5:28 ` Tejun Heo
2007-03-18 12:35 ` Jose Alberto Reguero
2007-03-18 13:48 ` Tejun Heo [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=45FD4330.1020108@gmail.com \
--to=htejun@gmail.com \
--cc=jareguero@telefonica.net \
--cc=jeff@garzik.org \
--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).