From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux PM list <linux-pm@vger.kernel.org>,
mark gross <markgross@thegnar.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
"Len Brown (Intel)" <len.brown@intel.com>,
Magnus Damm <magnus.damm@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Arjan van de Ven <arjan@infradead.org>, Tejun Heo <tj@kernel.org>,
jean.pihet@newoldbits.com, Kevin Hilman <khilman@ti.com>,
Daniel Drake <dsd@laptop.org>,
ming.lei@canonical.com, Grant Likely <grant.likely@secretlab.ca>,
Mark Brown <broonie@sirena.org.uk>,
John Stultz <john.stultz@linaro.org>
Subject: [RFH] Power Management mini-summit during the Kernel Summit 2011
Date: Wed, 12 Oct 2011 22:11:21 +0200 [thread overview]
Message-ID: <201110122211.21638.rjw@sisk.pl> (raw)
Hi All,
There was a plan to organize a PM mini-summit during the KS 2011 in Prague,
but then I didn't follow up (which obviously is my fault) and lost track of
things when kernel.org and the KS servers went offline. So, apparently,
the KS organizers concluded that the PM mini-summit wasn't going to happen
after all and didn't add it to the schedule.
Still, it appears to be possible to arrange a room for a PM meeting on
Sunday, Oct 23, if there are people wanting to attend. So, if you'd like
to take part in such a meeting, please let me know ASAP.
The topics I, personally, would like to discuss include:
- Per-device PM QoS
- Propagation of wakeup events to user space vs system suspend
- Possibility of representing dependencies between devices through
"device links" (i.e. objects representing master-slave links between
devices)
- Idea of common "platform" bus type that may cover ACPI devices (like
battery, fans etc.), PNP devices and current platform devices in a
consistent way
- Freezer improvements
Thanks,
Rafael
next reply other threads:[~2011-10-12 20:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 20:11 Rafael J. Wysocki [this message]
2011-10-12 20:30 ` [RFH] Power Management mini-summit during the Kernel Summit 2011 Grant Likely
2011-10-13 10:34 ` Mark Brown
2011-10-12 20:33 ` Jean Pihet
2011-10-12 20:40 ` Greg KH
2011-10-12 22:22 ` Magnus Damm
2011-10-12 23:40 ` Kevin Hilman
2011-10-13 3:59 ` mark gross
2011-10-13 14:55 ` Daniel Drake
2011-10-13 16:04 ` Grant Likely
2011-10-13 19:05 ` Rafael J. Wysocki
2011-10-13 19:05 ` Grant Likely
2011-10-13 19:17 ` Rafael J. Wysocki
2011-10-13 19:52 ` Greg KH
2011-10-13 19:55 ` Grant Likely
2011-10-13 20:15 ` Greg KH
2011-10-13 21:33 ` Rafael J. Wysocki
2011-10-13 22:35 ` Grant Likely
2011-10-15 22:35 ` Rafael J. Wysocki
2011-10-16 4:20 ` Grant Likely
2011-10-16 14:42 ` Rafael J. Wysocki
2011-10-17 0:38 ` joeyli
2011-10-17 22:05 ` Rafael J. Wysocki
2011-10-17 3:46 ` Grant Likely
2011-10-17 22:06 ` Rafael J. Wysocki
2011-10-13 21:20 ` Jean Pihet
2011-10-13 21:27 ` Rafael J. Wysocki
2011-10-13 21:26 ` Kevin Hilman
2011-10-13 21:50 ` Magnus Damm
2011-10-13 22:38 ` Grant Likely
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=201110122211.21638.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arjan@infradead.org \
--cc=broonie@sirena.org.uk \
--cc=dsd@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=jean.pihet@newoldbits.com \
--cc=john.stultz@linaro.org \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=markgross@thegnar.org \
--cc=ming.lei@canonical.com \
--cc=mjg59@srcf.ucam.org \
--cc=tj@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