From: Chris Wilson <chris@chris-wilson.co.uk>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
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 21:03:22 +0000 [thread overview]
Message-ID: <0d30dc$km57aq@orsmga001.jf.intel.com> (raw)
In-Reply-To: <AANLkTinY5XysANA9Qd-h=U8wzDNjF4n0sSxMsXH4P+99@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]
On Thu, 6 Jan 2011 21:55:23 +0100, Alex Riesen <raa.lkml@gmail.com> wrote:
> On Thu, Jan 6, 2011 at 18:49, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > 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);
> > }
>
> FWIW it does not compile:
> CC drivers/gpu/drm/i915/intel_lvds.o
> drivers/gpu/drm/i915/intel_lvds.c: In function ‘intel_lvds_enable’:
> drivers/gpu/drm/i915/intel_lvds.c:110: error: ‘PPS_STATUS’ undeclared
> (first use in this function)
> drivers/gpu/drm/i915/intel_lvds.c:110: error: (Each undeclared
> identifier is reported only once
> drivers/gpu/drm/i915/intel_lvds.c:110: error: for each function it appears in.)
> make[4]: *** [drivers/gpu/drm/i915/intel_lvds.o] Error 1
Daniel quickly pointed out my typo: s/PPS_STATUS/PP_STATUS/
Apologies,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-06 21:03 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
2011-01-06 20:55 ` Alex Riesen
2011-01-06 21:03 ` Chris Wilson [this message]
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='0d30dc$km57aq@orsmga001.jf.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=raa.lkml@gmail.com \
--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