From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Albert Lee <albertcc@tw.ibm.com>, Jens Axboe <axboe@suse.de>,
Edward Falk <efalk@google.com>,
Carlos Pardo <Carlos.Pardo@siliconimage.com>,
Raymond Liu <Raymond.Liu@siliconimage.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [ANNOUNCE] libata EH/NCQ/hotplug/PM git tree
Date: Sat, 13 May 2006 00:09:59 -0400 [thread overview]
Message-ID: <44655C17.6000601@pobox.com> (raw)
In-Reply-To: <44655986.3060007@gmail.com>
Tejun Heo wrote:
> That cmd-switching PM support is what AHCI SPM bit indicates. As of
> v1.1, AHCI doesn't define FIS-switching PM support yet.
Right you are; see, told you my brain was frazzled.
> Which is understandable considering AHCI doesn't construct FISes itself.
> I don't think PM requires more hardware support than being capable for
> setting PMP in the FISes, which AHCI certainly can (standing down on
> collision for SDB notify aside). I can give it a shot but it clearly
> violates the spec, and even if it works, we would need to print big fat
> warning message while attaching PM.
Setting the PMP field during FIS construction would work, I should
think, for outgoing FIS's. Not sure how incoming FISs would behave.
Jeff
next prev parent reply other threads:[~2006-05-13 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 1:44 [ANNOUNCE] libata EH/NCQ/hotplug/PM git tree Tejun Heo
2006-05-10 4:51 ` zhao, forrest
2006-05-10 5:17 ` Tejun Heo
2006-05-10 5:36 ` zhao, forrest
2006-05-10 6:29 ` Raz Ben-Jehuda(caro)
2006-05-10 6:33 ` Tejun Heo
2006-05-10 13:37 ` Shem Multinymous
2006-05-10 16:44 ` Shem Multinymous
2006-05-11 3:09 ` zhao, forrest
2006-05-11 7:07 ` Tejun Heo
2006-05-13 1:30 ` Jeff Garzik
2006-05-13 1:36 ` Tejun Heo
2006-05-13 3:37 ` Jeff Garzik
2006-05-13 3:59 ` Tejun Heo
2006-05-13 4:09 ` Jeff Garzik [this message]
2006-05-13 4:19 ` Tejun Heo
2006-05-13 10:02 ` Stefan Smietanowski
2006-05-13 10:20 ` Tejun Heo
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=44655C17.6000601@pobox.com \
--to=jgarzik@pobox.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=Raymond.Liu@siliconimage.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=efalk@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.