From: Keith Packard <keithp@keithp.com>
To: Alex Davis <alex14641@yahoo.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mjg\@redhat.com" <mjg@redhat.com>,
Kamal Mostafa <kamal@canonical.com>
Subject: Re: [Regression] Laptop screen dark when lid closed and reopened.with 3.1
Date: Wed, 26 Oct 2011 08:13:14 -0700 [thread overview]
Message-ID: <yunmxcnhjlh.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1319599156.52195.YahooMailNeo@web130106.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Tue, 25 Oct 2011 20:19:16 -0700 (PDT), Alex Davis <alex14641@yahoo.com> wrote:
> At the request of Kamal Mostafa, an Ubuntu kernel developer, I am resubmitting this patch which fixes my backlight issue.
> It seem that there are a number of people with different machines that have this problem:
We have a patch that should land in a 3.1 stable release that should
resolve this issue; can you test that?
commit f52c619a590fa75276c07dfcaf380dee53e4ea4c
Author: Takashi Iwai <tiwai@suse.de>
Date: Fri Oct 14 11:45:40 2011 +0200
drm/i915/panel: Always record the backlight level again (but cleverly)
The commit 47356eb67285014527a5ab87543ba1fae3d1e10a introduced a
mechanism to record the backlight level only at disabling time, but it
also introduced a regression. Since intel_lvds_enable() may be called
without disabling (e.g. intel_lvds_commit() calls it unconditionally),
the backlight gets back to the last recorded value. For example, this
happens when you dim the backlight, close the lid and open the lid,
then the backlight suddenly goes to the brightest.
This patch fixes the bug by recording the backlight level always
when changed via intel_panel_set_backlight(). And,
intel_panel_{enable|disable}_backlight() call the internal function not
to update the recorded level wrongly.
Cc: <stable@kernel.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Reviewed-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Keith Packard <keithp@keithp.com>
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2011-10-26 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 0:28 [Regression] Laptop screen dark when lid closed and reopened Alex Davis
[not found] ` <CAHR1FHH9bJScYkD7_gDaSd1JZ7eMai+x_-gzUtRZ5jmLSft_WA@mail.gmail.com>
2011-09-20 3:35 ` Alex Davis
[not found] ` <CAHR1FHGAf-UFU2GTK_ZcdxFe2Ngxpf9RtnXeRUOtQ1Fz4mqE3A@mail.gmail.com>
2011-09-20 11:31 ` Pranjal Verma
2011-09-24 12:55 ` [Regression] Laptop screen dark when lid closed and reopened.with 3.1 Alex Davis
2011-09-24 14:48 ` Keith Packard
2011-09-24 15:13 ` Alex Davis
2011-09-24 17:40 ` Keith Packard
2011-09-25 13:23 ` Alex Davis
2011-09-25 20:29 ` Keith Packard
2011-09-25 20:48 ` Alex Davis
2011-09-27 10:16 ` Alex Davis
2011-09-27 17:55 ` Keith Packard
2011-10-02 19:20 ` Alex Davis
2011-10-02 21:09 ` Alex Davis
2011-10-26 3:19 ` Alex Davis
2011-10-26 15:13 ` Keith Packard [this message]
2011-10-26 20:21 ` Kamal Mostafa
2011-10-26 22:52 ` Alex Davis
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=yunmxcnhjlh.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=alex14641@yahoo.com \
--cc=kamal@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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