All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fix hdmi portclock limits
Date: Mon, 22 Jul 2013 18:35:16 +0200	[thread overview]
Message-ID: <20130722163516.GB5939@phenom.ffwll.local> (raw)
In-Reply-To: <20130722162434.GK8706@strange.amr.corp.intel.com>

On Mon, Jul 22, 2013 at 05:24:34PM +0100, Damien Lespiau wrote:
> On Mon, Jul 22, 2013 at 06:02:39PM +0200, Daniel Vetter wrote:
> > In
> > 
> > commit 325b9d048810f7689ec644595061c0b700e64bce
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date:   Fri Apr 19 11:24:33 2013 +0200
> > 
> >     drm/i915: fixup 12bpc hdmi dotclock handling
> > 
> > I've errornously claimed that we don't yet support the hdmi 1.4
> > dotclocks > 225 MHz on Haswell. But a bug report and a closer look at
> > the wrpll table showed that we've supported port clocks up to 300MHz.
> > 
> > With the new code to dynamically compute wrpll limits we should have
> > no issues going up to the full 340 MHz range of hdmi 1.4, so let's
> > just use that to fix this regression. That'll allow 4k over hdmi for
> > free!
> > 
> > v2: Drop the random hunk that somehow slipped in.
> > 
> > v3: Cantiga has the original HDMI dotclock limit of 165MHz. And also
> > patch up the mode filtering. To do so extract the dotclock limits into
> > a little helper function.
> > 
> > v4: Use 300MHz (from Bspec) instead of 340MHz (upper limit for hdmi
> > 1.3), apparently hw is not required to be able to drive the highest
> > dotclocks. Suggested by Damien.
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=67048
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=67030
> > Tested-by: Andreas Reis <andreas.reis@gmail.com> (v2)
> > Cc: Damien Lespiau <damien.lespiau@intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>

Picked up for -fixes, thanks for the review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-07-22 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 14:14 [PATCH] drm/i915: fix hdmi portclock limits on Haswell Daniel Vetter
2013-07-22  6:05 ` [PATCH] drm/i915: fix hdmi portclock limits Daniel Vetter
2013-07-22 11:11   ` Daniel Vetter
2013-07-22 11:17   ` Damien Lespiau
2013-07-22 14:36     ` Damien Lespiau
2013-07-22 16:02       ` Daniel Vetter
2013-07-22 16:24         ` Damien Lespiau
2013-07-22 16:35           ` Daniel Vetter [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=20130722163516.GB5939@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=damien.lespiau@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.