All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Andrzej Hajda <a.hajda@samsung.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v4 2/2] drm: Add HDMI 2.0 VIC support for AVI info-frames
Date: Thu, 23 Mar 2017 17:45:28 +0200	[thread overview]
Message-ID: <20170323154528.GW31595@intel.com> (raw)
In-Reply-To: <4ea0e5b5-b367-4fbf-142c-666dbde9aeb8@synopsys.com>

On Thu, Mar 23, 2017 at 03:28:29PM +0000, Jose Abreu wrote:
> Hi Shashank,
> 
> 
> On 23-03-2017 15:14, Shashank Sharma wrote:
> > HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
> > For any other mode, the VIC filed in AVI infoframes should be 0.
> > HDMI 2.0 sinks, support video modes range as per CEA-861-F spec, which is
> > extended to (VIC 1-107).
> >
> > This patch adds a bool input variable, which indicates if the connected
> > sink is a HDMI 2.0 sink or not. This will make sure that we don't pass a
> > HDMI 2.0 VIC to a HDMI 1.4 sink.
> >
> > This patch touches all drm drivers, who are callers of this function
> > drm_hdmi_avi_infoframe_from_display_mode but to make sure there is
> > no change in current behavior, is_hdmi2 is kept as false.
> >
> > In case of I915 driver, this patch checks the connector->display_info
> > to check if the connected display is HDMI 2.0.
> >
> > Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
> > Cc: Jose Abreu <jose.abreu@synopsys.com>
> > Cc: Andrzej Hajda <a.hajda@samsung.com>
> > Cc: Alex Deucher <alexander.deucher@amd.com>
> > Cc: Daniel Vetter <daniel.vetter@intel.com>
> >
> > PS: This patch touches a few lines in few files, which were
> > already above 80 char, so checkpatch gives 80 char warning again.
> > - gpu/drm/omapdrm/omap_encoder.c
> > - gpu/drm/i915/intel_sdvo.c
> >
> > Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
> > ---
> >  drivers/gpu/drm/amd/amdgpu/dce_v10_0.c    |  2 +-
> >  drivers/gpu/drm/amd/amdgpu/dce_v11_0.c    |  2 +-
> >  drivers/gpu/drm/amd/amdgpu/dce_v8_0.c     |  2 +-
> >  drivers/gpu/drm/bridge/analogix-anx78xx.c |  3 ++-
> >  drivers/gpu/drm/bridge/sii902x.c          |  2 +-
> >  drivers/gpu/drm/bridge/synopsys/dw-hdmi.c |  2 +-
> >  drivers/gpu/drm/drm_edid.c                | 12 +++++++++++-
> >  drivers/gpu/drm/exynos/exynos_hdmi.c      |  2 +-
> >  drivers/gpu/drm/i2c/tda998x_drv.c         |  2 +-
> >  drivers/gpu/drm/i915/intel_hdmi.c         |  5 ++++-
> >  drivers/gpu/drm/i915/intel_sdvo.c         |  3 ++-
> >  drivers/gpu/drm/mediatek/mtk_hdmi.c       |  2 +-
> >  drivers/gpu/drm/omapdrm/omap_encoder.c    |  3 ++-
> >  drivers/gpu/drm/radeon/radeon_audio.c     |  2 +-
> >  drivers/gpu/drm/rockchip/inno_hdmi.c      |  2 +-
> >  drivers/gpu/drm/sti/sti_hdmi.c            |  2 +-
> >  drivers/gpu/drm/tegra/hdmi.c              |  2 +-
> >  drivers/gpu/drm/tegra/sor.c               |  2 +-
> >  drivers/gpu/drm/vc4/vc4_hdmi.c            |  2 +-
> >  drivers/gpu/drm/zte/zx_hdmi.c             |  2 +-
> >  include/drm/drm_edid.h                    |  3 ++-
> >  21 files changed, 38 insertions(+), 21 deletions(-)
> >
> 
> [snip]
> 
> > diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
> > index af93f7a..5ff2886 100644
> > --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
> > +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
> > @@ -1146,7 +1146,7 @@ static void hdmi_config_AVI(struct dw_hdmi *hdmi, struct drm_display_mode *mode)
> >  	u8 val;
> >  
> >  	/* Initialise info frame from DRM mode */
> > -	drm_hdmi_avi_infoframe_from_display_mode(&frame, mode);
> > +	drm_hdmi_avi_infoframe_from_display_mode(&frame, mode, false);
> >  
> >  	if (hdmi->hdmi_data.enc_out_format == YCBCR444)
> >  		frame.colorspace = HDMI_COLORSPACE_YUV444;
> >
> 
> dw-hdmi controller has full support for HDMI 2.0 features. It all
> depends on the platform it is integrated.
> 
> I think adding a parameter to
> drm_hdmi_avi_infoframe_from_display_mode is not the best idea
> because of this case: A bridge can have support for HDMI 2.0
> features but the platform may limit this support. I guess it can
> happen in other drivers too.

Your driver is in full control of what gets passed here. So I don't see
why that would be a problem.

Also this doesn't really have anything to do with the capabilities of
the source. All we want to make sure is that we don't send a VIC the
sink will not understand.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-23 15:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 15:14 [PATCH v4 1/2] drm/edid: Complete CEA modedb(VIC 1-107) Shashank Sharma
2017-03-23 15:14 ` [PATCH v4 2/2] drm: Add HDMI 2.0 VIC support for AVI info-frames Shashank Sharma
2017-03-23 15:17   ` Ilia Mirkin
2017-03-23 15:22     ` Sharma, Shashank
2017-03-23 15:28       ` Ilia Mirkin
2017-03-23 16:33         ` Sharma, Shashank
2017-03-23 15:28   ` Jose Abreu
2017-03-23 15:45     ` Ville Syrjälä [this message]
2017-03-23 15:57       ` Jose Abreu
2017-03-23 16:08         ` Sharma, Shashank
2017-03-23 16:33           ` Jose Abreu
2017-03-23 16:43             ` Sharma, Shashank
2017-03-23 17:11               ` Jose Abreu
2017-03-23 17:42                 ` Ville Syrjälä
2017-03-23 17:53                   ` Jose Abreu
2017-03-23 18:14                     ` Ville Syrjälä
2017-03-23 18:35                       ` Jose Abreu
2017-03-23 15:36   ` Ville Syrjälä
2017-03-23 15:52     ` Jose Abreu
2017-03-23 16:31       ` Sharma, Shashank
2017-03-23 17:01         ` Ville Syrjälä
2017-03-23 16:01 ` ✓ Fi.CI.BAT: success for series starting with [v4,1/2] drm/edid: Complete CEA modedb(VIC 1-107) 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=20170323154528.GW31595@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=a.hajda@samsung.com \
    --cc=alexander.deucher@amd.com \
    --cc=daniel.vetter@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 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.