From: Kamal Mostafa <kamal@canonical.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: i915 PCH backlight vs. Dell XPS13
Date: Tue, 12 Feb 2013 10:35:14 -0800 [thread overview]
Message-ID: <1360694114.21346.85.camel@fourier> (raw)
In-Reply-To: <CAKMK7uG6GsFpZoLQJwUu1mi2b9dGuW_4sGvRunsAvSUhJ5XJGw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 774 bytes --]
On Fri, Feb 8, 2013 at 8:36 PM, Kamal Mostafa <kamal@canonical.com> wrote:
> > Daniel's backlight fixes which landed in 3.6 did enable working
> > backlight controls on the XPS13, but it appears that this commit from
> > Paolo broke it again:
> > a4f32fc drm/i915: don't forget the PCH backlight registers
On Fri, 2013-02-08 at 20:55 +0100, Daniel Vetter wrote:
> You might want to try the latest drm-intel-nightly git branch from
> http://cgit.freedesktop.org/~danvet/drm-intel This has a few more
> tricks which helped on some similar platforsm to yours (and similar
> resume issues).
Yes indeed, this commit from drm-intel-nightly does fix the problem:
"drm/i915: write backlight harder".
Thanks as always, for your help Daniel!
-Kamal
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2013-02-12 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1360352163.14891.44.camel@fourier>
2013-02-08 19:55 ` i915 PCH backlight vs. Dell XPS13 Daniel Vetter
2013-02-12 18:35 ` Kamal Mostafa [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=1360694114.21346.85.camel@fourier \
--to=kamal@canonical.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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