linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: alan@lxorguk.ukuu.org.uk, lkml@rtr.ca, axboe@suse.de,
	forrest.zhao@intel.com, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET] libata: implement runtime link powersave
Date: Mon, 24 Jul 2006 16:33:26 +0900	[thread overview]
Message-ID: <44C477C6.6070402@gmail.com> (raw)
In-Reply-To: <44BE8A25.9060804@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
>> Hello, all.
>>
>> This is the first take of powersave patchset.  It implements runtime
>> link-level power management.  To avoid confusion with regular
>> device/controller power management (suspend/resume), it's callsed
>> powersave.  It primarily implements partial/slumber/phy-off power
>> states SATA standard specifies but if LLD has different way of
>> implementing link powersave, it's allowed to.  Both host-initiated and
>> device-initiated operations are supported.
>>
>> This patchset contains the following patches.
>>
>> #01-07    : misc fixes/preps for powersave
>> #08-10    : implements core powersave infrastructure
>> #11-12    : implement powersave feature for ahci and sata_sil24
>>
>> Powersave can be configured at boot time or while running by writing
>> to kernel module parameter /sys/module/libata/parameters/powersave.
>> The following powersave modes are supported.
>>
>> * none        : no powersave, link is powered up all the time
>> * HIPS        : host-initiated powersave
>> * DIPS        : device-initiated powersave
>> * static    : no powersave on occupied link, power off empty link
>> * HIPS/static    : HIPS on occupied link, power off empty link
>> * DIPS/static    : DIPS on occupied link, power off empty link
>>
>> For more information, please read head messages of individual patches.
>>
>> All supported modes are tested on ICH7R AHCI, ICH6M AHCI, SiI3124,
>> SiI3132.  Unfortunately SiI3112/4 family controllers don't support
>> HIPS and choke on DIPS and thus dropped from supported list.
> 
> Any chance you tried ata_piix static PS, using PCS register?  :)

No, but I think both static and dynamic powersave can be implemented 
nicely on ICH8s as SCRs can be accessed on those controllers without 
mapping AHCI BAR.  Hmm.. yeah, STATIC powersave mode can be done with 
PCS although I'm pretty scared to mess with PCS at this point.  :(

-- 
tejun


      reply	other threads:[~2006-07-24  9:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  6:52 [PATCHSET] libata: implement runtime link powersave Tejun Heo
2006-07-17  6:52 ` [PATCH 03/12] libata: add more SATA specific constants and macros to ata.h Tejun Heo
2006-07-19 19:32   ` Jeff Garzik
2006-07-17  6:52 ` [PATCH 01/12] libata: add msec_to_jiffies() Tejun Heo
2006-07-17  6:52 ` [PATCH 04/12] libata: implement ata_all_ports list Tejun Heo
2006-07-19 19:34   ` Jeff Garzik
2006-07-17  6:52 ` [PATCH 02/12] libata: add ata_id_has_sata() and use it in ata_id_has_ncq() Tejun Heo
2006-07-17  6:52 ` [PATCH 06/12] libata: add ata_port_nr_ready() Tejun Heo
2006-07-17  6:52 ` [PATCH 07/12] libata: implement sata_update_scontrol() Tejun Heo
2006-07-19 19:35   ` Jeff Garzik
2006-07-17  6:52 ` [PATCH 09/12] libata: implement powersave timer Tejun Heo
2006-07-19 19:48   ` Jeff Garzik
2006-07-19 20:22     ` Jens Axboe
2006-07-24  7:27       ` Tejun Heo
2006-07-25  8:01         ` Jens Axboe
2006-07-17  6:52 ` [PATCH 05/12] libata: make counting functions global Tejun Heo
2006-07-17  6:52 ` [PATCH 10/12] libata: implement standard powersave methods Tejun Heo
2006-07-19 19:50   ` Jeff Garzik
2006-07-17  6:52 ` [PATCH 08/12] libata: implement interface power management infrastructure Tejun Heo
2006-07-19 19:45   ` Jeff Garzik
2006-07-24  8:02     ` Tejun Heo
2006-07-17  6:52 ` [PATCH 11/12] ahci: implement link powersave Tejun Heo
2006-07-19 19:51   ` Jeff Garzik
2006-07-17  6:52 ` [PATCH 12/12] sata_sil24: " Tejun Heo
2006-07-19 19:38 ` [PATCHSET] libata: implement runtime " Jeff Garzik
2006-07-24  7:33   ` 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=44C477C6.6070402@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=forrest.zhao@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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).