From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: "Brown, Len" <len.brown@intel.com>,
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, 21 Jul 2015 00:21:32 +0200 [thread overview]
Message-ID: <2015360.EW9BxZmMXF@vostro.rjw.lan> (raw)
In-Reply-To: <CAKMK7uFmyH9Gc3EY6F24PK3hOtxLPYEi9U=ixe=g-3=amoQoCw@mail.gmail.com>
On Friday, July 17, 2015 01:41:56 PM Daniel Vetter wrote:
> On Thu, Jul 16, 2015 at 5:58 PM, Greg KH <greg@kroah.com> wrote:
> > On Thu, Jul 16, 2015 at 08:53:02AM -0700, Josh Triplett wrote:
> >> But the kernel already has quirk tables for various hardware, and that
> >> seems appropriate to continue putting in the kernel.
> >
> > For some types of devices, sure. For others, like broken USB keyboards
> > that can't handle autosuspend, no. For those we need a userspace
> > _whitelist_ that udev can use. So there's no one answer that works for
> > all types of quirks.
>
> Whether white or blacklist or some other mixed thing doesn't really
> matter. Imo the important part is that driver maintainers are in the
> best position to maintain that, and pushing it out to anyone else is
> just really not doing our jobs. And I think for most of these quirk
> lists the kernel does seem like the most appropriate place. If the
> list becomes giantic then we can move it to userspace (if that's
> really a problem, afaik no one proposed yet to move device match
> tables into userspace either and that's kinda the same thing really).
> But as long as there's no white/black/whatever list yet starting in
> the kernel is imo the right place.
Well, I'm wondering, then, why i915.enable_psr is not enabled by default,
for one example?
Failing to enable it prevents some SoCs from using the deepest available
C-states which in turn hurts battery life of the systems containing them
quite a bit, so there surely is a reason to have it enabled.
Thanks,
Rafael
next prev parent reply other threads:[~2015-07-20 21: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
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 [this message]
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=2015360.EW9BxZmMXF@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 \
/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