From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Iyer, Sundar" <sundar.iyer@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Kristen Carlson Accardi <kristen@linux.intel.com>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] System-wide interface to specify the level of PM tuning
Date: Mon, 06 Jul 2015 16:21:23 +0200 [thread overview]
Message-ID: <6142539.s1gh8ubrRK@vostro.rjw.lan> (raw)
In-Reply-To: <2FABAEF0D3DCAF4F9C9628D6E2F968454F18BA5A@BGSMSX102.gar.corp.intel.com>
On Monday, July 06, 2015 01:49:45 PM Iyer, Sundar wrote:
> > -----Original Message-----
> > From: ksummit-discuss-bounces@lists.linuxfoundation.org [mailto:ksummit-
> > discuss-bounces@lists.linuxfoundation.org] On Behalf Of Rafael J. Wysocki
> > Sent: Monday, July 6, 2015 7:12 AM
> > To: NeilBrown
> > Cc: Grant Likely; Brown, Len; Alan Stern; Kristen Carlson Accardi; ksummit-
> > discuss@lists.linuxfoundation.org
> > Subject: Re: [Ksummit-discuss] [TECH TOPIC] System-wide interface to specify
> > the level of PM tuning
> >
>
> > >
> > > (a tiny bit like a devicetree database which contains configuration
> > > rules).
> > >
> > > Or have I missed the point completely?
> >
> > No, I don't think you have missed it, but then most of subsystems and drivers in
> > the kernel know what it means to be "power-friendly", so they should be able to
> > choose their defaults on the basis of one single setting somewhere.
>
> Is a "single setting somewhere" even appropriate? It is actually the intelligence
> needed vs executing the actions?
For one example, the default for most of the device/.../power/control files in
sysfs is "on" (meaning no runtime PM) while it might be "auto" (use runtime PM
if you can). Making that change for everybody in one go may lead to various
issues (that may be regarded as regressions then), but if we made it configurable,
people might choose to make that change for themselves if they wanted to.
Thanks,
Rafael
next prev parent reply other threads:[~2015-07-06 13:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 0:22 Rafael J. Wysocki
2015-07-06 1:21 ` Josh Triplett
2015-07-06 14:04 ` Rafael J. Wysocki
2015-07-06 1:40 ` NeilBrown
2015-07-06 14:12 ` Rafael J. Wysocki
2015-07-06 13:49 ` Iyer, Sundar
2015-07-06 14:21 ` Rafael J. Wysocki [this message]
2015-07-07 7:53 ` Jiri Kosina
2015-07-07 12:33 ` Rafael J. Wysocki
2015-07-10 17:25 ` Kevin Hilman
2015-07-12 10:01 ` Daniel Vetter
2015-07-13 23:07 ` Rafael J. Wysocki
2015-07-14 16:51 ` Daniel Vetter
2015-07-15 22:44 ` Rafael J. Wysocki
2015-07-16 1:10 ` Josh Triplett
2015-07-16 9:19 ` David Woodhouse
2015-07-16 15:44 ` Kristen Accardi
2015-07-16 15:53 ` Josh Triplett
2015-07-16 15:58 ` Greg KH
2015-07-17 10:34 ` Takashi Iwai
2015-07-17 11:41 ` Daniel Vetter
2015-07-20 22:21 ` Rafael J. Wysocki
2015-07-20 23:09 ` Daniel Vetter
2015-07-22 1:12 ` Rafael J. Wysocki
2015-07-22 7:18 ` Daniel Vetter
2015-07-22 17:25 ` Rafael J. Wysocki
2015-07-22 18:25 ` josh
2015-07-24 22:36 ` Rafael J. Wysocki
2015-07-25 19:50 ` Josh Triplett
2015-07-26 0:03 ` Rafael J. Wysocki
2015-07-26 0:16 ` Josh Triplett
2015-07-27 13:30 ` Rafael J. Wysocki
2015-07-27 11:50 ` Jani Nikula
2015-07-06 16:33 ` Kristen Accardi
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=6142539.s1gh8ubrRK@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=grant.likely@linaro.org \
--cc=kristen@linux.intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=sundar.iyer@intel.com \
/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