All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fix hdmi portclock limits
Date: Mon, 22 Jul 2013 15:36:46 +0100	[thread overview]
Message-ID: <20130722143646.GI8706@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20130722111712.GC8706@strange.amr.corp.intel.com>

On Mon, Jul 22, 2013 at 12:17:12PM +0100, Damien Lespiau wrote:
> On Mon, Jul 22, 2013 at 08:05:10AM +0200, Daniel Vetter wrote:
> > +static int hdmi_portclock_limit(struct intel_hdmi *hdmi)
> > +{
> > +	struct drm_device *dev = intel_hdmi_to_dev(hdmi);
> > +
> > +	if (IS_G4X(dev))
> > +		return 165000;
> > +	else if (IS_HASWELL(dev))
> > +		return 340000;
> 
> I read 300MHz in the BSpec?

To expand a bit here, HDMI 1.3 and 1.4 have their upper limit defined to
340MHz, but not every piece of hardware is able to achieve that. In our
case the limit seems to be 300MHz for HSW (which apparently is already
enough for some 4k resolutions).

HDMI 1.x and QHD is not that interesting, it can only up to 30Hz. DP
seems the way to go there until HDMI 2.0

-- 
Damien

  reply	other threads:[~2013-07-22 14:36 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 [this message]
2013-07-22 16:02       ` Daniel Vetter
2013-07-22 16:24         ` Damien Lespiau
2013-07-22 16:35           ` Daniel Vetter

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=20130722143646.GI8706@strange.amr.corp.intel.com \
    --to=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.