From: Stefan Smietanowski <stesmi@stesmi.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
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 12:02:40 +0200 [thread overview]
Message-ID: <4465AEC0.30300@stesmi.com> (raw)
In-Reply-To: <44655986.3060007@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
Tejun Heo wrote:
> Jeff Garzik wrote:
>
>> Tejun Heo wrote:
>>
>>> Jeff Garzik wrote:
>>>
>>>> Tejun Heo wrote:
>>>>
>>>>> tested. I implemented AHCI PM support half-way but then realized I
>>>>> don't have any AHCI controller which supports PM (I have ICH7R).
>>>>> Is there any AHCI controller which reports PM support?
>>>>
>>>>
>>>> You can always use SCR-based PM support...
>>>>
>>>
>>> Can you elaborate a bit?
>>
>>
>> Sections A.1 and 6.1 of the PM spec. You set the PMP field of the
>> SControl register. This has obvious parallelism limitations, which is
>> why "hardware context switching support" aka native PM support is
>> greatly preferred.
>>
>
> That cmd-switching PM support is what AHCI SPM bit indicates. As of
> v1.1, AHCI doesn't define FIS-switching PM support yet.
>
> Supports Port Multiplier (SPM): Indicates whether the HBA can support a
> Port Multiplier. When set, a Port Multiplier using command-based
> switching is supported. When cleared to ‘0’, a Port Multiplier is not
> supported, and a Port Multiplier may not be attached to this HBA.
>
> And. the SControl section says...
>
> 19:16 RO 0h Port Multiplier Port (PMP): This field is not used by AHCI.
>
> 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.
>
Are you saying that the next big thing since sliced bread (AHCI) that's
supposed to unite the world and make everybody sing Kumbayah doesn't
support port multipliers (according to the spec) ?
Or am I totally misreading this.
// Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2006-05-13 10:02 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
2006-05-13 4:19 ` Tejun Heo
2006-05-13 10:02 ` Stefan Smietanowski [this message]
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=4465AEC0.30300@stesmi.com \
--to=stesmi@stesmi.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=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).