From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: Linux 2.6.37
Date: Thu, 06 Jan 2011 17:49:48 +0000 [thread overview]
Message-ID: <1bdc18$j6a1ns@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <AANLkTi=aTKFVO8Lx=fDUGrxVaQL73XrsxoOP7-qYKksb@mail.gmail.com>
On Thu, 6 Jan 2011 08:29:22 -0800, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Jan 6, 2011 at 2:48 AM, Michal Hocko <mhocko@suse.cz> wrote:
> >
> > It seems that there is still a regression for intel graphic cards
> > backlight. One report is https://bugzilla.kernel.org/show_bug.cgi?id=22672.
> > I can reproduce the problem easily by:
> > xset dpms force standby; sleep 3s; xset dpms force on
> >
> > backlight doesn't get up (there is really dark picture though which
> > doesn't get brighter by function keys which work normally) after dpms on
> > until I close and open lid.
>
> Hmm. That commit no longer reverts cleanly, so it's not trivial to
> test whether all those things are exactly the same issue. It's been
> bisected in the bugzilla entry, but it would be good to verify that
> yes, reverting it really does fix the issue, and your issue is the
> exact same one.
>
> Chris, any ideas?
My fear is that some machines have a dependency between the backlight
and panel power status. The patch in question changed the timing between
turning on the panel and adjusting the backlight which would be restore
with:
diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
index aa23070..0b40b4f 100644
--- a/drivers/gpu/drm/i915/intel_lvds.c
+++ b/drivers/gpu/drm/i915/intel_lvds.c
@@ -106,6 +106,12 @@ static void intel_lvds_enable(struct intel_lvds *intel_lvds)
I915_WRITE(ctl_reg, I915_READ(ctl_reg) | POWER_TARGET_ON);
POSTING_READ(lvds_reg);
+ {
+ u32 reg = HAS_PCH_SPLIT(dev) ? PCH_PP_STATUS : PPS_STATUS;
+ if (wait_for(I915_READ(reg) & PP_ON, 1000))
+ DRM_ERROR("timed out waiting for panel to power up\n");
+ }
+
intel_panel_set_backlight(dev, dev_priv->backlight_level);
}
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-06 17:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 1:15 Linux 2.6.37 Linus Torvalds
2011-01-06 10:48 ` Michal Hocko
2011-01-06 16:29 ` Linus Torvalds
2011-01-06 17:03 ` Michal Hocko
2011-01-06 17:49 ` Chris Wilson [this message]
2011-01-06 20:55 ` Alex Riesen
2011-01-06 21:03 ` Chris Wilson
2011-01-06 21:08 ` Alex Riesen
2011-01-07 15:52 ` Michal Hocko
2011-01-11 13:33 ` Pavel Machek
2011-01-11 14:28 ` Michal Hocko
2011-01-11 14:47 ` Alex Riesen
2011-01-11 17:19 ` Michal Hocko
2011-01-11 17:37 ` Michal Hocko
2011-01-11 18:37 ` Michal Hocko
2011-01-11 17:39 ` Chris Wilson
2011-01-11 17:44 ` Michal Hocko
2011-01-12 0:35 ` Indan Zupancic
2011-01-12 12:07 ` Chris Wilson
2011-01-12 12:14 ` Chris Wilson
2011-01-13 0:35 ` Indan Zupancic
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 19:20 Zephaniah E. Loss-Cutler-Hull
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='1bdc18$j6a1ns@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=torvalds@linux-foundation.org \
/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