From: Shashank Sharma <shashank.sharma@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
jose.abreu@synopsys.com, jani.nikula@linux.intel.com,
maarten.lankhorst@linux.intel.com, ville.syrjala@linux.intel.com
Cc: Ander Conselvan De Oliveira
<ander.conselvan.de.oliveira@intel.com>,
daniel.vetter@intel.com, treding@nvidia.com
Subject: [PATCH v4 6/6] drm/i915: allow HDMI 2.0 clock rates
Date: Wed, 22 Feb 2017 18:48:31 +0530 [thread overview]
Message-ID: <1487769511-17359-7-git-send-email-shashank.sharma@intel.com> (raw)
In-Reply-To: <1487769511-17359-1-git-send-email-shashank.sharma@intel.com>
Geminilake has a native HDMI 2.0 controller, which is capable of
driving clocks upto 594Mhz. This patch updates the max tmds clock
limit for the same.
V2: rebase
V3: rebase
V4: added r-b from Ander
Cc: Ander Conselvan De Oliveira <ander.conselvan.de.oliveira@intel.com>
Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
Reviewed-by: Ander Conselvan De Oliveira <ander.conselvan.de.oliveira@intel.com>
---
drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
index c44beee..84b4e29 100644
--- a/drivers/gpu/drm/i915/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/intel_hdmi.c
@@ -1210,6 +1210,8 @@ static int intel_hdmi_source_max_tmds_clock(struct drm_i915_private *dev_priv)
{
if (IS_G4X(dev_priv))
return 165000;
+ else if (IS_GEMINILAKE(dev_priv))
+ return 594000;
else if (IS_HASWELL(dev_priv) || INTEL_INFO(dev_priv)->gen >= 8)
return 300000;
else
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-22 13:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 13:18 [PATCH v4 0/6] HDMI 2.0: Scrambling in DRM layer Shashank Sharma
2017-02-22 13:18 ` [PATCH v4 1/6] drm: Add SCDC helpers Shashank Sharma
2017-02-22 17:09 ` Ville Syrjälä
2017-02-23 3:21 ` Sharma, Shashank
2017-02-23 11:41 ` Ville Syrjälä
2017-02-23 12:09 ` Sharma, Shashank
2017-02-22 13:18 ` [PATCH v4 2/6] drm/edid: check for HF-VSDB block Shashank Sharma
2017-02-22 13:18 ` [PATCH v4 3/6] drm/edid: detect SCDC support in HF-VSDB Shashank Sharma
2017-02-22 13:18 ` [PATCH v4 4/6] drm: scrambling support in drm layer Shashank Sharma
2017-02-22 17:24 ` Ville Syrjälä
2017-02-23 3:35 ` Sharma, Shashank
2017-02-23 11:45 ` Ville Syrjälä
2017-02-23 12:13 ` Sharma, Shashank
2017-02-22 13:18 ` [PATCH v4 5/6] drm/i915: enable scrambling Shashank Sharma
2017-02-22 17:29 ` Ville Syrjälä
2017-02-23 4:31 ` Sharma, Shashank
2017-02-23 8:03 ` Ander Conselvan De Oliveira
2017-02-23 11:03 ` Sharma, Shashank
2017-02-23 13:07 ` Ander Conselvan De Oliveira
2017-02-23 13:21 ` Ville Syrjälä
2017-02-23 15:16 ` Sharma, Shashank
2017-02-22 13:18 ` Shashank Sharma [this message]
2017-02-22 17:22 ` ✓ Fi.CI.BAT: success for HDMI 2.0: Scrambling in DRM layer (rev4) Patchwork
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=1487769511-17359-7-git-send-email-shashank.sharma@intel.com \
--to=shashank.sharma@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jose.abreu@synopsys.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=treding@nvidia.com \
--cc=ville.syrjala@linux.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