From: Mark Lord <lkml@rtr.ca>
To: Pavel Machek <pavel@ucw.cz>
Cc: Mark Lord <liml@rtr.ca>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
stern@rowland.harvard.edu, linux-ide@vger.kernel.org
Subject: Re: [ugly patch] Save .15W-.5W by AHCI powersaving
Date: Tue, 26 Feb 2008 10:52:36 -0500 [thread overview]
Message-ID: <47C435C4.9000402@rtr.ca> (raw)
In-Reply-To: <20080225223432.GN2659@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>>> This is a patch (very ugly, assumes you have just one disk) to bring
>>> powersaving to AHCI. You need Alan's SCSI autosuspend (attached) patch
>>> as a base.
>>>
>>> It saves .5W compared to config with disk spinning, and even .15W
>>> compared to hdparm -y... on my thinkpad x60 anyway.
>> ..
>>
>> There was a discussion of this here today.
>
> Real-life discussion, or something I could read? :-).
>
>> It makes good use of AHCI-specific features.
>>
>> Has it been tested with a Port-Multiplier yet?
>
> I do not know what port-multiplier is, sorry. But it was not really
> tested. It is not expected to work on any other config than notebook
> very similar to mine.
>
>> This is cool enough that we really ought to do a hardware-independent
>> version, so that all SATA interfaces could benefit. Especially ata_piix,
>> but others too.
>
> Well, it seems like it is 10 lines per driver once Alan's SCSI
> autosuspend patches are in...
..
Cool (literally)!
I think I might have gotten your patch confused in my mind
with another AHCI patch, which uses features of the chip itself
to automatically negotiate/change link power status on the fly
(no s/w needed, other than to turn it on).
That one is very ACPI specific, though.
next prev parent reply other threads:[~2008-02-26 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 13:45 [ugly patch] Save .15W-.5W by AHCI powersaving Pavel Machek
2008-02-25 22:26 ` Mark Lord
2008-02-25 22:34 ` Pavel Machek
2008-02-26 15:52 ` Mark Lord [this message]
2008-02-26 21:49 ` Pavel Machek
2008-02-25 22:42 ` Jeff Garzik
2008-02-26 16:21 ` Matthew Garrett
2008-03-21 7:49 ` Oliver Neukum
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=47C435C4.9000402@rtr.ca \
--to=lkml@rtr.ca \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
/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).