From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kamal Mostafa <kamal@canonical.com>
Cc: linux-acpi@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC PATCH 0/2] i915 brightness control
Date: Mon, 13 Sep 2010 18:48:48 +0100 [thread overview]
Message-ID: <20100913174847.GA10443@srcf.ucam.org> (raw)
In-Reply-To: <1275516702-27090-1-git-send-email-kamal@canonical.com>
On Wed, Jun 02, 2010 at 03:11:40PM -0700, Kamal Mostafa wrote:
> In order to avoid the often-dysfunctional native acpi brightness control
> methods, a new acpi_brightness_hook interface is made available.
>
> The i915 driver uses the new hook to take over brightness control.
> Boot with i915.brightness=0 to disable.
I've looked into this issue more closely and think I've worked out the
underlying problem. The system in question appears to have two GPUs and
exposes two ACPI backlight devices. Both of these are associated with
existing PCI devices, so we don't ignore either of them because of that.
Further, one of them (the AMD one) implements the spec properly and
should work. We don't seem to perform a more fine-grained check to
identify whether every ACPI backlight has all the required methods, and
so as a result we provide both the working one and the non-working one.
Having thought about this some more, I don't think this is the right
approach. We should be ensuring that every backlight ahs all the
required methods and then dropping the one that doesn't. This should be
replaced with a native i915 backlight, and I sent patches to do that
last week.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-09-13 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 22:11 [RFC PATCH 0/2] i915 brightness control Kamal Mostafa
2010-06-02 22:11 ` [RFC PATCH 1/2] acpi/video: acpi_brightness_hook API Kamal Mostafa
2010-06-02 22:11 ` [RFC PATCH 2/2] drm/i915: override acpi brightness control Kamal Mostafa
2010-06-02 23:20 ` [Intel-gfx] [RFC PATCH 0/2] i915 " Pedro Ribeiro
2010-06-03 14:19 ` Matthew Garrett
2010-06-04 19:47 ` Jerone Young
2010-09-13 17:48 ` Matthew Garrett [this message]
2010-09-24 19:12 ` Kamal Mostafa
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=20100913174847.GA10443@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kamal@canonical.com \
--cc=linux-acpi@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