public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Dave Airlie <airlied@redhat.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	daniel.vetter@intel.com, jani.nikula@linux.intel.com
Subject: 4.0 -> 4.1 regression : after resume from s2ram both internal and external display of a docked ThinkPad ate black
Date: Thu, 3 Dec 2015 17:06:59 +0100	[thread overview]
Message-ID: <20151203160659.GB31751@amd> (raw)
In-Reply-To: <56333A8A.3000707@gmx.de>

> >>> commit e7d6f7d708290da1b7c92f533444b042c79412e0
> >>> Author: Dave Airlie <airlied@redhat.com>
> >>> Date:   Mon Dec 8 13:23:37 2014 +1000
> >>>
> >>>     drm/i915: resume MST after reading back hw state
....
> >> Is there anything else what I can do ?
> >>
> >> Current kernels up to 4.2.3 and 4.3-rc3 (not hardened) shows this issue here at my system.
> > 
> > Yes. Now you ask Dave Airlie <airlied@redhat.com> to fix it. If that
> 
> Dear Dave,
> 
> please fix it.
> 
> Here's a work around which works for me since kernel 4.1.x :

Dave. You broke it. You fix it. Don't make me less polite?

Daniel? Jani? Can you apply the patch below, or comment whats wrong
with that?

This is a regression, so it should not require much thinking.

									Pavel

> diff --git a/drivers/gpu/drm/i915/i915_drv.c
> b/drivers/gpu/drm/i915/i915_drv.c
> index ab64d68..3aeead2 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -740,6 +740,8 @@ static int i915_drm_resume(struct drm_device *dev)
>         if (dev_priv->display.hpd_irq_setup)
>                 dev_priv->display.hpd_irq_setup(dev);
>         spin_unlock_irq(&dev_priv->irq_lock);
> +
> +       intel_dp_mst_resume(dev);
> 
>         drm_modeset_lock_all(dev);
>         intel_display_resume(dev);
> 
> 
> > does not work, you ask him to fix it, in less polite words. If that
> > does not work, you verify that reverting
> > e7d6f7d708290da1b7c92f533444b042c79412e0 fixes it for you, then ask
> > Daniel Vetter and Jani Nikula to revert it. If they fail to do that,
> > you go all the way up to Linus.
> > 
> > Good luck ;-), 
> > 									Pavel
> > 
> 
> 

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2015-12-03 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 13:54 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black Toralf Förster
2015-08-02  7:43 ` Pavel Machek
2015-08-03  9:53   ` Toralf Förster
2015-08-03 18:50     ` Toralf Förster
2015-08-04 12:29   ` Toralf Förster
2015-08-15 13:32     ` Toralf Förster
2015-10-04 16:30     ` Toralf Förster
2015-10-29 21:49       ` Pavel Machek
2015-10-30  9:38         ` Toralf Förster
2015-12-03 16:06           ` Pavel Machek [this message]

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=20151203160659.GB31751@amd \
    --to=pavel@ucw.cz \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.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