Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 1/1] drm/i915/cnl: Extend HDMI 2.0 support to CNL.
Date: Mon, 13 Nov 2017 10:47:44 -0800	[thread overview]
Message-ID: <20171113184744.3adablcnhgjwii34@intel.com> (raw)
In-Reply-To: <93ced317-d488-c0a1-1072-d6389664f2df@intel.com>

On Sat, Nov 11, 2017 at 09:43:44AM +0000, Sharma, Shashank wrote:
> Regards
> 
> Shashank
> 
> 
> On 11/11/2017 3:56 AM, Rodrigo Vivi wrote:
> > Starting on GLK we support HDMI 2.0. So this patch only
> > extend the work Shashank has made to GLK to CNL.
> > 
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Cc: Shashank Sharma <shashank.sharma@intel.com>
> > Cc: Manasi Navare <manasi.d.navare@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> >   drivers/gpu/drm/i915/intel_hdmi.c | 7 ++++---
> >   1 file changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> > index 2d95db64cdf2..1b22b587e98c 100644
> > --- a/drivers/gpu/drm/i915/intel_hdmi.c
> > +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> > @@ -1235,7 +1235,7 @@ static int intel_hdmi_source_max_tmds_clock(struct intel_encoder *encoder)
> >   		&dev_priv->vbt.ddi_port_info[encoder->port];
> >   	int max_tmds_clock;
> > -	if (IS_GEMINILAKE(dev_priv))
> > +	if (IS_GEMINILAKE(dev_priv) || INTEL_GEN(dev_priv) >= 10)
> Would it be a good idea to create a new macro called IS_HDMI2_SUPPORTED() or
> a function is_hdmi2_supported() where we keep all the GEN check ?

I asked myself the same question.
I believe a IS_HDMI2_SUPPORTED or HAS_HDMI2_SUPPORT is a good idea...

> >   		max_tmds_clock = 594000;
> >   	else if (INTEL_GEN(dev_priv) >= 8 || IS_HASWELL(dev_priv))
> >   		max_tmds_clock = 300000;
> > @@ -1511,7 +1511,8 @@ bool intel_hdmi_compute_config(struct intel_encoder *encoder,
> >   	pipe_config->lane_count = 4;
> > -	if (scdc->scrambling.supported && IS_GEMINILAKE(dev_priv)) {
> > +	if (scdc->scrambling.supported && (IS_GEMINILAKE(dev_priv) ||
> > +					   INTEL_GEN(dev_priv) >= 10) {
> >   		if (scdc->scrambling.low_rates)
> >   			pipe_config->hdmi_scrambling = true;
> > @@ -2033,7 +2034,7 @@ void intel_hdmi_init_connector(struct intel_digital_port *intel_dig_port,
> >   	connector->doublescan_allowed = 0;
> >   	connector->stereo_allowed = 1;
> > -	if (IS_GEMINILAKE(dev_priv))
> > +	if (IS_GEMINILAKE(dev_priv) || INTEL_GEN(dev_priv) >= 10)
> >   		connector->ycbcr_420_allowed = true;
> Looks good otherwise.
> - Shashank
> >   	intel_hdmi->ddc_bus = intel_hdmi_ddc_pin(dev_priv, port);
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-13 18:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 22:26 [PATCH 0/1] HDMI 2.0 on CNL... not working Rodrigo Vivi
2017-11-10 22:26 ` [PATCH 1/1] drm/i915/cnl: Extend HDMI 2.0 support to CNL Rodrigo Vivi
2017-11-10 22:45   ` [PATCH] " Rodrigo Vivi
2017-11-10 23:50   ` [PATCH 1/1] " Manasi Navare
2017-11-11  0:04     ` Rodrigo Vivi
2017-11-11  9:47       ` Sharma, Shashank
2017-11-13 18:46         ` Rodrigo Vivi
2017-11-11  9:43   ` Sharma, Shashank
2017-11-13 18:47     ` Rodrigo Vivi [this message]
2017-11-15 19:05       ` David Weinehall
2017-11-17 13:09         ` Jani Nikula
2017-11-10 22:42 ` ✗ Fi.CI.BAT: failure for HDMI 2.0 on CNL... not working Patchwork
2017-11-10 23:17 ` ✓ Fi.CI.BAT: success for HDMI 2.0 on CNL... not working... (rev2) Patchwork
2017-11-11  1:13 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-12 23:29 ` [PATCH 0/1] HDMI 2.0 on CNL... not working Mike Lothian
2017-11-13 18:45   ` Rodrigo Vivi

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=20171113184744.3adablcnhgjwii34@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=shashank.sharma@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