All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Indan Zupancic <indan@nul.nu>,
	intel-gfx@lists.freedesktop.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 1/4] drm/i915: save/restore the legacy backlight control
Date: Tue, 28 Aug 2012 09:48:28 +0200	[thread overview]
Message-ID: <20120828074828.GA5125@phenom.ffwll.local> (raw)
In-Reply-To: <051c15$44688s@AZSMGA002.ch.intel.com>

On Tue, Aug 28, 2012 at 08:16:54AM +0100, Chris Wilson wrote:
> On Tue, 28 Aug 2012 09:53:36 +0300, Jani Nikula <jani.nikula@intel.com> 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.
> 
> My presumption was that there were BIOSes out there that only adjusted
> the LBPC values, and so any device setting that flag would likely only
> with it through the BIOS hotkeys. I couldn't see any other rational
> reason for the hardware maintaining multiple interfaces...

I've run a hackish version of this through a few bug reports and they
reported that there's no more black screen at boot-up, but also that the
backlight doesn't work. My conclusion was:
- there are machines that are only controlled through the lbpc reg
- some of those use lbpc in an inverted sense
- we have now idea how to figure out the sense of lbpc

Hence my thinking is that we should avoid to touch lbpc (but just restore
it across suspend/resume since some machines need that) and rely on any
firmware madness to properly adjust the backlight. I also realize that
this will regress machines without working firmware, but for which the
current lbpc-adjusting mess seems to do the right thing.

But if the only regression this causes is some non-working backlight
adjusting I'll ignore that, since it looks like we fundamentally can't do
the right thing with lbpc, and this series here should kill a few black
screen bugs.

Cheers, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-08-28  7:48 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 [this message]
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
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=20120828074828.GA5125@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.