mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: linux-kernel@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [2.6.39] drm/i915: blank screen on Lenovo Ideapad U160
Date: Wed, 15 Jun 2011 14:41:32 -0700	[thread overview]
Message-ID: <20110615144132.074167f3@jbarnes-desktop> (raw)
In-Reply-To: <giips6lr5a.fsf@mx10.gouders.net>

On Wed, 15 Jun 2011 23:29:53 +0200
Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> wrote:
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_d
> > index 81a9059..ef41487 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -1366,7 +1366,7 @@ static void intel_disable_pch_ports(struct drm_i915_privat
> >         val = I915_READ(reg);
> >         if (ADPA_PIPE_ENABLED(val, pipe))
> >                 I915_WRITE(reg, val & ~ADPA_DAC_ENABLE);
> > -
> > +#if 0
> >         reg = PCH_LVDS;
> >         val = I915_READ(reg);
> >         if (LVDS_PIPE_ENABLED(val, pipe)) {
> > @@ -1374,7 +1374,7 @@ static void intel_disable_pch_ports(struct drm_i915_privat
> >                 POSTING_READ(reg);
> >                 udelay(100);
> >         }
> > -
> > +#endif
> >         disable_pch_hdmi(dev_priv, pipe, HDMIB);
> >         disable_pch_hdmi(dev_priv, pipe, HDMIC);
> >         disable_pch_hdmi(dev_priv, pipe, HDMID);
> 
> No, that patch does not help.

Oh is this not an LVDS panel?  I'm curious which of the port disables
is at fault in your config then.  If you have an eDP panel, it would
likely be the PCH_DP_D write.  It could be a side effect of the
PANEL_UNLOCK_REGS write as well though, can you try commenting each of
those out?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-06-15 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 17:57 [3.0-rc1] i915: " Dirk Gouders
2011-05-31 18:08 ` Robert P. J. Day
2011-05-31 18:37   ` Dirk Gouders
2011-05-31 19:29     ` Dirk Gouders
2011-06-13 21:21       ` [2.6.39] drm/i915: " Dirk Gouders
2011-06-15 18:59         ` Jesse Barnes
2011-06-15 21:29           ` Dirk Gouders
2011-06-15 21:41             ` Jesse Barnes [this message]
2011-06-15 22:03               ` Dirk Gouders
2011-06-15 22:07                 ` Jesse Barnes
2011-06-16  7:38                   ` Dirk Gouders
2011-06-16 11:49                     ` Dirk Gouders
2011-06-16 16:40                       ` Jesse Barnes
2011-06-16 17:54                         ` Dirk Gouders
2011-06-16 18:41                           ` Jesse Barnes
2011-06-18 11:11                             ` Dirk Gouders

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=20110615144132.074167f3@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=gouders@et.bocholt.fh-gelsenkirchen.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®