From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Jiri Kosina <jkosina@suse.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: Tue, 07 Jul 2015 14:33:12 +0200 [thread overview]
Message-ID: <1447490.YSpEUg0Pqm@vostro.rjw.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1507070948590.10183@pobox.suse.cz>
On Tuesday, July 07, 2015 09:53:44 AM Jiri Kosina wrote:
> On Mon, 6 Jul 2015, Rafael J. Wysocki wrote:
>
> > 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),
>
> I don't believe that the current default settings are set the way they are
> set because we intentionally want to prefer performance to power efficiency.
No, this is not the intent, but having those defaults favors performance as
a consequence (and increasingly so as the integration of systems increases).
> The real problem is that it's really the only "safe" default,
> because turning power-management features on is likely to cause
> unpredictable issues (being it either real bugs in code, or just bad user
> experience stemming from unexpected system behavior).
>
> Such as suspended keyboard losing first keypress during wakeup (very
> common). Or wireless power management not working properly between the
> client and AP. Etc etc.
Agreed.
On the other hand, though, there are systems without those problems and their
users should be able to choose a more power-oriented behavior relatively
easily.
Thanks,
Rafael
next prev parent reply other threads:[~2015-07-07 12:07 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
2015-07-07 7:53 ` Jiri Kosina
2015-07-07 12:33 ` Rafael J. Wysocki [this message]
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=1447490.YSpEUg0Pqm@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=grant.likely@linaro.org \
--cc=jkosina@suse.com \
--cc=kristen@linux.intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=len.brown@intel.com \
--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