From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Tippett, Matthew" <Matthew.Tippett@amd.com>
Cc: "Langsdorf, Mark" <mark.langsdorf@amd.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, "Li, Samuel" <Samuel.Li@amd.com>
Subject: Re: [PATCH]AC/DC notifier
Date: Wed, 12 Aug 2009 01:55:32 +0100 [thread overview]
Message-ID: <20090812005532.GA31003@srcf.ucam.org> (raw)
In-Reply-To: <FFAE0590FF35E441901B67BD8BA62E950245ABD9@storexmb3.amd.com>
On Tue, Aug 11, 2009 at 08:51:49PM -0400, Tippett, Matthew wrote:
> From a graphics perspective (your area of expertise), this will allow KMS
> drivers to do some more intelligent actions based on the ac/dc state.
> Some examples of this could be improving the power consumption of the
> graphics hardware through adapting clock memory/engine settings for
> reduced power consumption, reducing refresh rate of the display to reduce
> scanout memory access, adjusting backlight brightness, etc.
Right. As you say, my concern is that most of this should belong in
userspace. Where we risk hardware damage there's an obvious argument for
doing this in kernel, but we should ensure that that's limited to
whatever coarse-grain handling is absolutely required rather than doing
things like touching display brightness.
--
Matthew Garrett | mjg59@srcf.ucam.org
next parent reply other threads:[~2009-08-12 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FFAE0590FF35E441901B67BD8BA62E950245ABD9@storexmb3.amd.com>
2009-08-12 0:55 ` Matthew Garrett [this message]
2009-08-14 16:32 ` [PATCH][ACPI] AC/DC notifier Pavel Machek
2009-08-16 7:40 ` [PATCH]AC/DC notifier Willy Tarreau
2009-10-06 14:53 ` Tippett, Matthew
2009-10-07 7:31 ` [PATCH][ACPI] AC/DC notifier Pavel Machek
2009-10-07 8:16 ` Dave Airlie
2009-10-07 14:05 ` [PATCH]AC/DC notifier Matthew Garrett
2009-10-07 17:00 ` [PATCH][ACPI] AC/DC notifier Tippett, Matthew
2009-08-11 20:15 Mark Langsdorf
2009-08-11 23:49 ` [PATCH]AC/DC notifier Matthew Garrett
2009-10-06 17:56 ` Len Brown
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=20090812005532.GA31003@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Matthew.Tippett@amd.com \
--cc=Samuel.Li@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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;
as well as URLs for NNTP newsgroup(s).