From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bryan Freed <bfreed@chromium.org>
Cc: airlied@linux.ie, airlied@redhat.com, ben@decadent.org.uk,
eric@anholt.net, mateusz.kaduk@gmail.com,
chris@chris-wilson.co.uk, bgamari.foss@gmail.com,
apw@canonical.com, yakui.zhao@intel.com, zhenyuw@linux.intel.com,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] Implement direct pineview backlight control.
Date: Fri, 2 Jul 2010 16:12:30 -0700 [thread overview]
Message-ID: <20100702161230.09f7c348@virtuousgeek.org> (raw)
In-Reply-To: <1277251107-24828-1-git-send-email-bfreed@chromium.org>
On Tue, 22 Jun 2010 16:58:27 -0700
Bryan Freed <bfreed@chromium.org> wrote:
> drm/i915: Add a direct interface for pineview backlight support.
>
> This adds a Kconfig variable CONFIG_DRM_I915_DIRECT_BACKLIGHT to
> optionally include the new source file i915_backlight.c. This file
> registers a couple backlight set/get routines with the standard
> drivers/video/backlight interface to add a directory under
> /sys/class/backlight/.
>
> The big problem I see with this modification is that the i915 driver
> _already_ supports backlight level adjustment in i915_opregion.c.
> Unfortunately, that requires an IRQ to occur as the result of writing
> some ASLE (ACPI Source Language Event) register, and this requires
> BIOS support for the ACPI hook. It looks like we will not have such
> support in our initial custom BIOS.
>
> So I copy a small amount of code from i915_opregion.c to make backlight
> adjustment directly available to the backlight framework.
>
> Another problem is that I do not cover all the cases handled by the
> i915_opregion.c code. It would be too much untested code copying to
> do so. I enforce the lack of support by checking for IS_PINEVIEW()
> in i915_backlight_init().
>
> Review URL: http://codereview.chromium.org/2830015
> Signed-off-by: Bryan Freed <bfreed@chromium.org>
How does this compare to Matthew's native backlight support? AFAIK
that patch is still outstanding due to the need for some changes to the
backlight subsystem.
Matthew?
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-07-02 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 23:58 Bryan Freed
2010-07-02 23:12 ` Jesse Barnes [this message]
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=20100702161230.09f7c348@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=apw@canonical.com \
--cc=ben@decadent.org.uk \
--cc=bfreed@chromium.org \
--cc=bgamari.foss@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mateusz.kaduk@gmail.com \
--cc=mjg@redhat.com \
--cc=yakui.zhao@intel.com \
--cc=zhenyuw@linux.intel.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
Powered by JetHome