From: Daniel Vetter <daniel@ffwll.ch>
To: Indan Zupancic <indan@nul.nu>
Cc: Jani Nikula <jani.nikula@intel.com>, Takashi Iwai <tiwai@suse.de>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915: save/restore the legacy backlight control
Date: Tue, 28 Aug 2012 17:15:34 +0200 [thread overview]
Message-ID: <20120828151534.GE5125@phenom.ffwll.local> (raw)
In-Reply-To: <4f206dd76bb01291ea6740c90ac392cc.squirrel@webmail.greenhost.nl>
On Tue, Aug 28, 2012 at 04:49:15PM +0200, Indan Zupancic wrote:
> On Tue, August 28, 2012 16:14, Daniel Vetter wrote:
> > On Tue, Aug 28, 2012 at 03:56:31PM +0200, Indan Zupancic wrote:
> >> Hello,
> >>
> >> On Tue, August 28, 2012 08:53, Jani Nikula wrote:
> >> > From: Daniel Vetter <daniel.vetter@ffwll.ch>
> >> >
> >> > This is a prep patch to stop drm/i915 from changing the LBPC registers
> >> > itself - but we still need to properly save/restore it on
> >> > suspend/resume.
> >> >
> >> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> >> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >> > ---
> [...]
> >> It seems weird that LBPC wouldn't be restored during resume by some BIOSes,
> >> is this really necessary?
> >
> > ba3820ade317ee36e496b9b40d2ec3987dd4aef0 claims so. But that commit
> > managed to put too many things into the same thing unfortunately.
>
> Is that the right SHA? Because that just reverts my combination mode
> removal patch. Assuming it is the right commit, then I think it's
> incorrect in saying that it caused backlight dimming problems after
> resume. That particular problem was caused by a bogus shift. The
> problems caused by removing the mode was a lower max brightness
> and/or less brightness levels.
Yeah, right commit but imo with sub-par commit message. Your other mail
clarified things, thanks.
> By the way, saving LBPC only makes sense if it's done before it was
> set to 0 to disable the panel. I don't know if the current code does
> the right thing, I haven't looked at it for a while.
I think we can coax it into doing the right thing, see my other mail. If
your completely sure that lbpc /should/ be handled by the bios across s/r
I think we can drop this. But tbh I have no idea how this really is
supposed to work, and unfortunately we're not allowed to cross-check with
the windows driver codebase :(
Thanks, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-08-28 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 6:53 [PATCH 0/4] drm/i915: backlight fixes and cleanup Jani Nikula
2012-08-28 6:53 ` [PATCH 1/4] drm/i915: save/restore the legacy backlight control Jani Nikula
2012-08-28 7:16 ` Chris Wilson
2012-08-28 7:48 ` Daniel Vetter
2012-08-28 13:56 ` Indan Zupancic
2012-08-28 14:14 ` Daniel Vetter
2012-08-28 14:49 ` Indan Zupancic
2012-08-28 15:15 ` Daniel Vetter [this message]
2012-08-30 8:32 ` Indan Zupancic
2012-08-30 8:50 ` Daniel Vetter
2012-08-28 6:53 ` [PATCH 2/4] drm/i915: remove combination mode for backlight control, again Jani Nikula
2012-08-28 14:39 ` Indan Zupancic
2012-08-28 14:55 ` Daniel Vetter
2012-08-30 9:29 ` Indan Zupancic
2012-11-14 16:48 ` Jesse Barnes
2012-08-28 6:53 ` [PATCH 3/4] drm/i915: remove brightness inversion quirk for acer aspire 5734z Jani Nikula
2012-08-28 6:53 ` [PATCH 4/4] drm/i915: remove module parameter and quirk for inverting brightness Jani Nikula
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=20120828151534.GE5125@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=indan@nul.nu \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=tiwai@suse.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