From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
jeff@garzik.org, james.bottomley@steeleye.com,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [patch 0/3] AHCI Link Power Management
Date: Tue, 12 Jun 2007 08:56:00 -0700 [thread overview]
Message-ID: <20070612085600.72d02b19.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <466E23AF.9060002@gmail.com>
On Tue, 12 Jun 2007 13:40:15 +0900
Tejun Heo <htejun@gmail.com> wrote:
> I don't think the end result will vary in any significant way. My
> biggest argument for sw implementation is it can be used for other
> controllers.
What I had in mind when I created the new port operation "enable_pm"
was that other controllers (besides the ahci controller) could define their
own method of enabling power management. Maybe for non-ahci controllers this
is a software based solution which uses generic SATA dipm/hipm stuff and
polling.
See patch 2/3 of this series for the implementation of this.
Kristen
next prev parent reply other threads:[~2007-06-12 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 18:46 Kristen Carlson Accardi
2007-06-12 1:58 ` Tejun Heo
2007-06-12 2:33 ` Jeff Garzik
2007-06-12 2:34 ` Arjan van de Ven
2007-06-12 3:12 ` Jeff Garzik
2007-06-12 3:12 ` Arjan van de Ven
2007-06-12 3:18 ` Jeff Garzik
2007-06-12 4:13 ` Tejun Heo
2007-06-12 4:19 ` Arjan van de Ven
2007-06-12 4:40 ` Tejun Heo
2007-06-12 15:56 ` Kristen Carlson Accardi [this message]
2007-06-12 4:43 ` Jeff Garzik
2007-06-12 15:43 ` Kristen Carlson Accardi
2007-06-13 14:51 ` Pavel Machek
2007-06-13 9:04 ` Pavel Machek
2007-06-13 16:26 ` Kristen Carlson Accardi
2007-06-14 7:56 ` Tejun Heo
2007-06-13 14:56 ` Pavel Machek
2007-06-14 11:56 ` Jens Axboe
2007-06-14 12:30 ` 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=20070612085600.72d02b19.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=arjan@linux.intel.com \
--cc=htejun@gmail.com \
--cc=james.bottomley@steeleye.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®