From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Shashank Sharma <shashank.sharma@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
ville.syrjala@linux.intel.com
Subject: Re: [Intel-gfx] [RESEND-CI v4 15/15] drm/i915/glk: set HDMI 2.0 identifier
Date: Fri, 30 Jun 2017 15:07:43 +0300 [thread overview]
Message-ID: <1498824463.3311.5.camel@gmail.com> (raw)
In-Reply-To: <1498041253-16426-15-git-send-email-shashank.sharma@intel.com>
On Wed, 2017-06-21 at 16:04 +0530, Shashank Sharma wrote:
> This patch sets the is_hdmi2_src identifier in drm connector
> for GLK platform. GLK contains a native HDMI 2.0 controller.
> This identifier will help the EDID handling functions to save
> lot of work which is specific to HDMI 2.0 sources.
>
> V3: Added this patch
> V4: Rebase
>
> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
This and patches 12 and 14 look fine to me. I'm not sure about the patch split,
maybe they should be squashed together in the end? And perhaps patch 10 and 13
too if the refactor I proposed are separate prep patches. But anyway, you can
use
Reviewed-by: Ander Conselvan de Oliveira <conselvan2@gmail.com>
on those if you want.
> ---
> drivers/gpu/drm/i915/intel_hdmi.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> index 3bd9af3..0d9d088 100644
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1979,6 +1979,9 @@ 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))
> + connector->ycbcr_420_allowed = true;
> +
> intel_hdmi->ddc_bus = intel_hdmi_ddc_pin(dev_priv, port);
>
> switch (port) {
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-30 12:07 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 10:33 [RESEND-CI v4 00/15] HDMI YCBCR output handling in DRM layer Shashank Sharma
2017-06-21 10:33 ` [RESEND-CI v4 01/15] drm: add HDMI 2.0 VIC support for AVI info-frames Shashank Sharma
2017-06-21 13:41 ` Neil Armstrong
2017-06-30 11:54 ` Ville Syrjälä
2017-07-03 9:06 ` Sharma, Shashank
2017-07-03 9:57 ` Ville Syrjälä
2017-07-03 11:24 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 02/15] drm: add YCBCR 420 capability identifier Shashank Sharma
2017-06-21 13:42 ` Neil Armstrong
2017-06-21 10:34 ` [RESEND-CI v4 03/15] drm/edid: Complete CEA modedb(VIC 1-107) Shashank Sharma
2017-06-21 13:42 ` Neil Armstrong
2017-06-27 11:32 ` Ville Syrjälä
2017-06-30 5:11 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 04/15] drm/edid: parse YCBCR 420 videomodes from EDID Shashank Sharma
2017-06-27 11:52 ` Ville Syrjälä
2017-06-30 5:17 ` Sharma, Shashank
2017-06-30 11:58 ` Ville Syrjälä
2017-06-30 12:08 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 05/15] drm/edid: parse ycbcr 420 deep color information Shashank Sharma
2017-06-27 11:53 ` Ville Syrjälä
2017-06-30 5:20 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 06/15] drm/edid: parse sink information before CEA blocks Shashank Sharma
2017-06-27 11:55 ` Ville Syrjälä
2017-06-30 5:22 ` Sharma, Shashank
2017-06-30 11:46 ` Ville Syrjälä
2017-06-30 12:01 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 08/15] drm: set output colorspace in AVI infoframe Shashank Sharma
2017-06-21 10:34 ` [RESEND-CI v4 09/15] drm: add helper functions for YCBCR output handling Shashank Sharma
2017-06-22 7:05 ` [Intel-gfx] " Daniel Vetter
2017-06-22 9:42 ` Sharma, Shashank
2017-06-23 9:12 ` Daniel Vetter
2017-06-23 10:01 ` [Intel-gfx] " Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 10/15] drm/i915: add compute-config for YCBCR outputs Shashank Sharma
2017-06-21 10:34 ` [RESEND-CI v4 11/15] drm/i915: prepare scaler for YCBCR420 modeset Shashank Sharma
2017-06-27 12:16 ` Ander Conselvan De Oliveira
2017-06-30 5:50 ` Sharma, Shashank
2017-06-30 11:34 ` Ander Conselvan De Oliveira
2017-06-30 11:59 ` Sharma, Shashank
2017-06-30 14:15 ` Ander Conselvan De Oliveira
2017-06-30 14:27 ` Sharma, Shashank
2017-06-21 10:34 ` [RESEND-CI v4 12/15] drm/i915: prepare pipe for YCBCR output Shashank Sharma
2017-06-21 10:34 ` [RESEND-CI v4 13/15] drm/i915: prepare csc unit for YCBCR HDMI output Shashank Sharma
2017-06-29 12:08 ` Ander Conselvan De Oliveira
2017-06-30 6:03 ` Sharma, Shashank
2017-06-30 10:57 ` Ander Conselvan De Oliveira
2017-06-21 10:34 ` [RESEND-CI v4 14/15] drm/i915: set colorspace for ycbcr outputs Shashank Sharma
2017-06-21 10:34 ` [RESEND-CI v4 15/15] drm/i915/glk: set HDMI 2.0 identifier Shashank Sharma
2017-06-30 12:07 ` Ander Conselvan De Oliveira [this message]
2017-06-30 12:17 ` Sharma, Shashank
2017-06-30 13:28 ` [Intel-gfx] " Ander Conselvan De Oliveira
2017-06-21 10:34 ` [PATCH v5 7/7] drm: create hdmi output property Shashank Sharma
2017-06-22 7:14 ` [Intel-gfx] " Daniel Vetter
2017-06-22 8:33 ` Sharma, Shashank
2017-06-23 9:20 ` [Intel-gfx] " Daniel Vetter
2017-06-23 10:05 ` Sharma, Shashank
2017-06-23 10:28 ` Daniel Vetter
2017-06-27 12:14 ` Ville Syrjälä
2017-06-30 5:43 ` Sharma, Shashank
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=1498824463.3311.5.camel@gmail.com \
--to=conselvan2@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shashank.sharma@intel.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;
as well as URLs for NNTP newsgroup(s).