From: Kevin Hilman <khilman@ti.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Grant Likely <grant.likely@secretlab.ca>,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>,
Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Len Brown <lenb@kernel.org>
Subject: Re: [RFC][PATCH] Power domains for platform bus type
Date: Mon, 31 Jan 2011 15:43:41 -0800 [thread overview]
Message-ID: <871v3s3ahe.fsf@ti.com> (raw)
In-Reply-To: <201102010010.46096.rjw@sisk.pl> (Rafael J. Wysocki's message of "Tue, 1 Feb 2011 00:10:45 +0100")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
>> Also, what is the use case for having 2 sets of power_domain ops? My
>> gut tells me that you'd only want to do post ops on the
>> {freeze,suspend,poweroff} path and pre ops on the {resume,thaw,restore}
>> path. It seems overly engineered to me, but I may be missing
>> something fundamental.
>
> Well, that's a part of the RFC, actually. :-)
>
> For the subsystems I've worked with (PCI, ACPI, PNP to some extent) one set
> would be sufficient, but I don't know of every possible use case.
For the on-chip SoC devices we're managing with OMAP, we're currently
only using one set: post ops on [runtime_]suspend and pre ops on
[runtime_]resume.
However, I could imagine (at least conceptually) using the pre ops on
suspend to do some constraints checking and/or possibly some
management/notification of dependent devices. Another possiblity
(although possibly racy) would be using the pre ops on suspend to
initiate some high-latency operations.
I guess the main problem with two sets is wasted space. e.g, if I move
OMAP to this (already hacking on it) there will be only 2 functions used
in post ops: [runtime_]suspend() and 2 used in pre ops [runtime_]_resume().
Kevin
next prev parent reply other threads:[~2011-01-31 23:43 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 0:07 [RFC][PATCH] Power domains for platform bus type Rafael J. Wysocki
2011-01-30 16:03 ` Alan Stern
2011-01-30 22:39 ` Rafael J. Wysocki
2011-01-31 15:01 ` Alan Stern
2011-01-31 18:09 ` Rafael J. Wysocki
2011-01-31 19:45 ` Alan Stern
2011-01-31 22:16 ` Rafael J. Wysocki
2011-01-31 22:26 ` Grant Likely
2011-01-31 22:44 ` Kevin Hilman
2011-01-31 23:01 ` Rafael J. Wysocki
2011-01-31 12:05 ` Mark Brown
2011-01-31 22:59 ` Grant Likely
2011-01-31 23:10 ` Rafael J. Wysocki
2011-01-31 23:43 ` Kevin Hilman [this message]
2011-02-01 3:18 ` Grant Likely
2011-02-01 10:58 ` Rafael J. Wysocki
2011-02-01 16:48 ` Kevin Hilman
2011-02-01 18:39 ` Rafael J. Wysocki
2011-02-12 22:12 ` [RFC][PATCH 0/2] PM: Core power management modifications Rafael J. Wysocki
2011-02-12 22:13 ` [RFC][PATCH 1/2] PM: Add support for device power domains Rafael J. Wysocki
2011-02-14 16:12 ` Alan Stern
2011-02-14 22:34 ` Rafael J. Wysocki
2011-02-15 3:01 ` Alan Stern
2011-02-15 21:40 ` Rafael J. Wysocki
2011-02-15 7:28 ` Magnus Damm
2011-02-15 23:12 ` Rafael J. Wysocki
2011-02-15 18:23 ` Kevin Hilman
2011-02-12 22:14 ` [RFC][PATCH 2/2] PM: Make system-wide PM and runtime PM handle subsystems consistently Rafael J. Wysocki
2011-02-14 16:25 ` Alan Stern
2011-02-14 22:35 ` Rafael J. Wysocki
2011-02-16 12:24 ` Rafael J. Wysocki
2011-02-16 14:57 ` Alan Stern
2011-02-16 21:47 ` Rafael J. Wysocki
2011-02-16 22:23 ` Alan Stern
2011-02-16 23:45 ` Rafael J. Wysocki
2011-02-17 14:55 ` Alan Stern
2011-02-17 17:04 ` Greg KH
2011-02-17 22:16 ` Rafael J. Wysocki
2011-02-17 23:54 ` [PATCH] PM: Make system-wide PM and runtime PM treat " R. J. Wysocki
2011-02-18 19:22 ` Greg KH
2011-02-18 20:14 ` Rafael J. Wysocki
2011-02-15 18:10 ` [RFC][PATCH 2/2] PM: Make system-wide PM and runtime PM handle " Kevin Hilman
2011-02-15 19:48 ` Grant Likely
2011-02-01 3:40 ` [RFC][PATCH] Power domains for platform bus type Alan Stern
2011-01-31 23:16 ` Kevin Hilman
2011-01-31 23:23 ` Grant Likely
2011-02-01 0:17 ` Kevin Hilman
2011-02-01 10:52 ` Rafael J. Wysocki
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=871v3s3ahe.fsf@ti.com \
--to=khilman@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
--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).