public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: prefer wide & slow to fast & narrow in DP configs
Date: Wed, 4 Jul 2012 09:42:09 +0200	[thread overview]
Message-ID: <20120704074209.GD5375@phenom.ffwll.local> (raw)
In-Reply-To: <1340387615_42474@CP5-2952>

On Fri, Jun 22, 2012 at 06:53:01PM +0100, Chris Wilson wrote:
> On Fri, 22 Jun 2012 10:40:22 -0700, Keith Packard <keithp@keithp.com> wrote:
> > Chris Wilson <chris@chris-wilson.co.uk> writes:
> > 
> > > On Thu, 21 Jun 2012 18:13:19 -0700, Keith Packard <keithp@keithp.com> wrote:
> > 
> > > It was structured to minimise lane count because certain chipsets did
> > > not wire up all the lanes, right? Is that still relevant as we are using
> > > the advertised max_lane_count from the DPCD now?
> > 
> > We've always used the max_lane_count from dpcd; has there been some
> > recent change that fixed usage of that? What I recall is one acer laptop
> > that advertised 4 lanes but had only wired up two of them.
> 
> The only recentish change was your
> 
> commit 9a10f401a401ca69c6537641c8fc0d6b57b5aee8
> Author: Keith Packard <keithp@keithp.com>
> Date:   Wed Nov 2 13:03:47 2011 -0700
> 
>     drm/i915: Use DPCD value for max DP lanes.
> 
>     The BIOS VBT value for an eDP panel has been shown to be incorrect on
>     one machine, and we haven't found any machines where the DPCD value
>     was wrong, so we'll use the DPCD value everywhere.
> 
> We can but hope that no manufacturer lies in the DPCD.

Ok, I've merged this patch because it fixes a regression and this commit
Chris has dug out seems to indicate that we won't hit any known issues on
eDP panels. I guess if it blows up again, we'll have to take another look.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-07-04  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 22:13 [PATCH] drm/i915: prefer wide & slow to fast & narrow in DP configs Jesse Barnes
2012-06-22  1:13 ` Keith Packard
2012-06-22  9:05   ` Chris Wilson
2012-06-22 14:21     ` Adam Jackson
2012-06-22 16:29     ` Jesse Barnes
2012-06-22 17:42       ` Keith Packard
2012-06-22 17:40     ` Keith Packard
2012-06-22 17:53       ` Chris Wilson
2012-07-04  7:42         ` Daniel Vetter [this message]
2012-08-06  0:12           ` [3.2.y, 3.4.y, 3.5.y] " Jonathan Nieder

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=20120704074209.GD5375@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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