public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Paulo Zanoni <paulo.r.zanoni@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "drm/i915: try to train DP even harder"
Date: Mon, 18 Mar 2013 10:10:45 +0100	[thread overview]
Message-ID: <s5hboahul7u.wl%tiwai@suse.de> (raw)
In-Reply-To: <20130317215922.GH9021@phenom.ffwll.local>

At Sun, 17 Mar 2013 22:59:22 +0100,
Daniel Vetter wrote:
> 
> On Mon, Mar 11, 2013 at 06:40:16PM +0100, Takashi Iwai wrote:
> > This reverts commit 0d71068835e2610576d369d6d4cbf90e0f802a71.
> > 
> > Not only that the commit introduces a bogus check (voltage_tries == 5
> > will never meet at the inserted code path), it brings the i915 driver
> > into an endless dp-train loop on HP Z1 desktop machine with IVY+eDP.
> > 
> > At least reverting this commit recovers the framebuffer (but X is
> > still broken by other reasons...)
> > 
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Picked up for -fixes, thanks for the patch.

Thanks!

> Adding Paulo since it's his
> patch. To assign proper blame please cc: relevant people when sending out
> reverts.

Well, Paulo was on Cc in the first post, but I dropped in the next
patch series since I've got no reply since then.  (And intel-gfx was
on Cc, so he  could read it anyway...)


Takashi

      reply	other threads:[~2013-03-18  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 17:40 [PATCH] Revert "drm/i915: try to train DP even harder" Takashi Iwai
2013-03-17 21:59 ` Daniel Vetter
2013-03-18  9:10   ` Takashi Iwai [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=s5hboahul7u.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulo.r.zanoni@intel.com \
    /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