From: Danny Baumann <dannybaumann@web.de>
To: David Airlie <airlied@linux.ie>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Danny Baumann <dannybaumann@web.de>
Subject: [PATCH 0/1] drm/i915: Allow specifying a minimum brightness level for sysfs control.
Date: Tue, 26 Mar 2013 12:48:44 +0100 [thread overview]
Message-ID: <1364298525-4337-1-git-send-email-dannybaumann@web.de> (raw)
This patch makes the behaviour of the intel_backlight backlight device
consistent to e.g. acpi_videoX: When writing the value 0, the set brightness
makes the panel content barely readable instead of turning the backlight off.
This matches the expectations of user space (e.g. kde-workspace or the Intel
X11 driver), which expects that it can use intel_backlight as a drop-in
replacement for acpi_videoX.
As BIOSes written for Windows 8 support seem to expect the display driver
taking care of the brightness control instead of ACPI methods (see [1]),
I would expect quite a number of people (like me ;) ) having the need of
using intel_backlight instead of acpi_videoX. A quick Google search
indicated that most people are confused by the current behaviour, so I think
it's a good idea to make the default behaviour somehow match acpi_videoX.
Regards,
Danny
[1] https://bugzilla.kernel.org/show_bug.cgi?id=55071
Danny Baumann (1):
drm/i915: Allow specifying a minimum brightness level for sysfs
control.
drivers/gpu/drm/i915/intel_panel.c | 48 ++++++++++++++++++++++++++++++++------
1 file changed, 41 insertions(+), 7 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-03-26 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 11:48 Danny Baumann [this message]
2013-03-26 11:48 ` [PATCH 1/1] " Danny Baumann
2013-03-26 15:13 ` Daniel Vetter
2013-03-26 15:20 ` Chris Wilson
2013-03-26 17:04 ` Danny Baumann
2013-03-26 16:55 ` Danny Baumann
2013-03-26 17:02 ` [PATCH 0/1] " Matthew Garrett
2013-03-26 17:10 ` Danny Baumann
2013-03-26 17:21 ` Matthew Garrett
2013-03-27 11:56 ` Danny Baumann
2013-03-27 12:35 ` Alex Deucher
2013-03-27 12:56 ` Danny Baumann
2013-03-27 13:06 ` Alex Deucher
2013-03-27 15:10 ` Matthew Garrett
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=1364298525-4337-1-git-send-email-dannybaumann@web.de \
--to=dannybaumann@web.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.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
Powered by JetHome