dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: HDMI 4k support
Date: Wed,  7 Aug 2013 19:39:12 +0100	[thread overview]
Message-ID: <1375900754-3574-1-git-send-email-damien.lespiau@intel.com> (raw)

This series parses one of the dark corners of the EDID to expose "4k x 2k"
modes to userspace. Those modes are part of HDMI 1.4.

To complete the 4k HDMI support, one needs:

  * Hardware able to output a 300 MHz TMDS clock (Haswell can do that) and
    Daniel's patch to bump that limit in the kernel (already queued).

      Author: Daniel Vetter <daniel.vetter@ffwll.ch>
      Date:   Mon Jul 22 18:02:39 2013 +0200

          drm/i915: fix hdmi portclock limits

  * The 2 patches attached here to parse the HDMI VICs in the HDMI vendor
    specific CEA block.

  * A DDX patch (for UXA) already merged (and in 2.21.14)

      Author: Damien Lespiau <damien.lespiau@intel.com>
      Date:   Wed Jul 31 18:50:51 2013 +0100

          uxa/display: Keep the EDID blob around for the lifetime of an output

  * My "Use the TMDS maximum frequency to check mode dot clock" xserver series:

    http://lists.x.org/archives/xorg-devel/2013-August/037297.html

The bug referencing all that and the testing by QA:

  https://bugs.freedesktop.org/show_bug.cgi?id=67030
    
Additionally, edid-decode has been taught about those modes as well:

  http://lists.freedesktop.org/archives/dri-devel/2013-August/043078.html

-- 
Damien

             reply	other threads:[~2013-08-07 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 18:39 Damien Lespiau [this message]
2013-08-07 18:39 ` [PATCH 1/2] drm/edid: Fix add_cea_modes() style issues Damien Lespiau
2013-08-07 19:48   ` Ville Syrjälä
2013-08-07 18:39 ` [PATCH 2/2] drm/edid: Parse the HDMI CEA block and look for 4k modes Damien Lespiau
2013-08-07 19:45   ` Ville Syrjälä

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=1375900754-3574-1-git-send-email-damien.lespiau@intel.com \
    --to=damien.lespiau@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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