From: Chris Wilson <chris@chris-wilson.co.uk>
To: Carsten Emde <C.Emde@osadl.org>, David Airlie <airlied@linux.ie>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Keith Packard <keithp@keithp.com>,
Paul Menzel <paulepanter@users.sourceforge.net>,
Carsten Emde <C.Emde@osadl.org>,
DRI <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [V3 PATCH 2/2] drivers-gpu-drm-i915-quirk-backlight-inverted.patch
Date: Thu, 15 Mar 2012 10:09:15 +0000 [thread overview]
Message-ID: <c55c5d$2a7hsj@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120315095357.607004685@osadl.org>
On Thu, 15 Mar 2012 10:52:21 +0100, Carsten Emde <C.Emde@osadl.org> wrote:
> Following the documentation of the Legacy Backlight Brightness (LBB)
> Register in the configuration space of some Intel PCI graphics adapters,
> setting the LBB register with the value 0x0 causes the backlight to be
> turned off, and 0xFF causes the backlight to be set to 100% intensity
> (http://download.intel.com/embedded/processors/Whitepaper/324567.pdf).
> The Acer Aspire 5734Z, however, turns the backlight off at 0xFF and sets
> it to maximum intensity at 0. In consequence, the screen of this systems
> becomes dark at an early boot stage which makes it unusable. The same
> inversion applies to the BLC_PWM_CTL I915 register. This problem was
> introduced in kernel version 2.6.38 when the PCI device of this system
> was first supported by the i915 KMS module.
>
> This patch adds a quirk to invert the sense of the brightness variable
> in case an Acer Aspire 5734Z is encountered.
>
> Signed-off-by: Carsten Emde <C.Emde@osadl.org>
That looks a lot better. However, can I ask for another follow-on patch
to enable this quirk by a module parameter as well? I would like to make
it easier for anyone else hitting this issue to identity the problem and
find a temporary solution until their machine is also quirked.
> static void intel_init_quirks(struct drm_device *dev)
> Index: linux-3.3-rc7/drivers/gpu/drm/i915/intel_panel.c
> ===================================================================
> --- linux-3.3-rc7.orig/drivers/gpu/drm/i915/intel_panel.c
> +++ linux-3.3-rc7/drivers/gpu/drm/i915/intel_panel.c
> @@ -28,6 +28,7 @@
> * Chris Wilson <chris@chris-wilson.co.uk>
> */
>
> +#include <linux/moduleparam.h>
> #include "intel_drv.h"
That include is now not required.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-03-15 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 9:52 [V3 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware Carsten Emde
2012-03-15 9:52 ` [V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch Carsten Emde
2012-03-15 10:30 ` Bastien ROUCARIES
2012-03-15 10:45 ` Carsten Emde
2012-03-15 15:01 ` el es
2012-03-15 9:52 ` [V3 PATCH 2/2] drivers-gpu-drm-i915-quirk-backlight-inverted.patch Carsten Emde
2012-03-15 10:09 ` Chris Wilson [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='c55c5d$2a7hsj@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=C.Emde@osadl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulepanter@users.sourceforge.net \
--cc=tglx@linutronix.de \
/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