From: Kamal Mostafa <kamal@canonical.com>
To: Keith Packard <keithp@keithp.com>
Cc: Alex Davis <alex14641@yahoo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mjg@redhat.com" <mjg@redhat.com>
Subject: Re: [Regression] Laptop screen dark when lid closed and reopened.with 3.1
Date: Wed, 26 Oct 2011 13:21:40 -0700 [thread overview]
Message-ID: <1319660500.4206.120.camel@fourier> (raw)
In-Reply-To: <yunmxcnhjlh.fsf@aiko.keithp.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Wed, 2011-10-26 at 08:13 -0700, Keith Packard wrote:
> 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)
That patch (f52c619a) does not fix the problem on my Dell Studio 1558.
Alex's proposed patch -- removing the intel_panel_set_backlight(dev, 0)
call from intel_panel_disable_backlight -- does fix the problem
completely for me.
Please forgive the silly question, but why does
intel_panel_disable_backlight even want to set the brightness to 0
anyway?... Its only caller is just about to turn off power to the
panel.
Is that call to intel_panel_{,actually_}set_backlight(dev, 0) really
necessary or useful on *any* systems?
-Kamal
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-26 20:21 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
2011-10-26 20:21 ` Kamal Mostafa [this message]
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=1319660500.4206.120.camel@fourier \
--to=kamal@canonical.com \
--cc=alex14641@yahoo.com \
--cc=keithp@keithp.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