From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Port-Multiplier hotplug support: ATA_FLAG_AN
Date: Wed, 14 May 2008 08:46:11 -0400 [thread overview]
Message-ID: <482ADF13.7020701@rtr.ca> (raw)
In-Reply-To: <482A582A.7090108@gmail.com>
Tejun Heo wrote:
> Mark Lord wrote:
>> Tejun,
>>
>> Apparently the newer (GenIIe) sata_mv chips *can* support asynchronous
>> notification without problems. Some/all of the older ones cannot
>> (errata).
>>
>> So, I've done the one-liner change in sata_mv, to add ATA_FLAG_AN to
>> the 7042 and 6042 chips, and it all seems to work rather nicely.
>>
>> Am I missing something? Is there any other local code to sata_mv
>> that should be provided before setting ATA_FLAG_AN ?
>>
>> Like I said, it works, but I just want to check whether any other
>> pieces are expected to be present?
>
> You need to call sata_async_notification() from interrupt handler after
> AN FIS is received. sata_async_notification() is responsible for
> discerning between ATAPI and PMP ANs using SNotification and schedule
> appropriate actions. If SNotification is not available && PMP is
> attached, it just calls ata_port_schedule_eh(). That's probably why it
> just worked by setting ATA_FLAG_AN.
..
Okay, that's cool. So mv_err_intr() now just calls sata_async_notification(),
and then bails out without further action (if no other errors coincided),
and the EH then runs for just that one PM link, rather than the whole port.
(tested, working).
Cool!
prev parent reply other threads:[~2008-05-14 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 22:50 Port-Multiplier hotplug support: ATA_FLAG_AN Mark Lord
2008-05-13 23:25 ` Jeff Garzik
2008-05-14 2:50 ` Mark Lord
2008-05-14 3:10 ` Tejun Heo
2008-05-14 12:46 ` Mark Lord [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=482ADF13.7020701@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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).