From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 08/20] drm: set output colorspace in AVI infoframe
Date: Thu, 13 Jul 2017 18:19:01 +0530 [thread overview]
Message-ID: <189e3351-3c58-9854-ab4b-e21938aea3ca@intel.com> (raw)
In-Reply-To: <20170713123547.GV12629@intel.com>
Regards
Shashank
On 7/13/2017 6:05 PM, Ville Syrjälä wrote:
> On Thu, Jul 13, 2017 at 10:37:53AM +0530, Sharma, Shashank wrote:
>> Regards
>>
>> Shashank
>>
>>
>> On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
>>> On Mon, Jul 10, 2017 at 04:48:36PM +0530, Shashank Sharma wrote:
>>>> A source must set output colorspace information in AVI
>>>> infoframes, so that the sink can decode upcoming frames
>>>> accordingly.
>>>>
>>>> This patch adds a function to add the output colorspace
>>>> information in the AVI infoframes.
>>>>
>>>> V2: Rebase
>>>> V3: Rebase
>>>> V4: Rebase
>>>> V5: Rebase
>>>> V6: Made patch independent of HDMI output type.
>>>>
>>>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>>>> ---
>>>> drivers/gpu/drm/drm_edid.c | 29 +++++++++++++++++++++++++++++
>>>> include/drm/drm_edid.h | 5 +++++
>>>> 2 files changed, 34 insertions(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>>>> index 944a28f..cede86e 100644
>>>> --- a/drivers/gpu/drm/drm_edid.c
>>>> +++ b/drivers/gpu/drm/drm_edid.c
>>>> @@ -4796,6 +4796,35 @@ drm_hdmi_avi_infoframe_from_display_mode(struct hdmi_avi_infoframe *frame,
>>>> EXPORT_SYMBOL(drm_hdmi_avi_infoframe_from_display_mode);
>>>>
>>>> /**
>>>> + * drm_hdmi_avi_infoframe_set_colorspace - fill an HDMI AVI infoframe with
>>>> + * colorspace data of the output type
>>>> + *
>>>> + * @frame: HDMI AVI infoframe
>>>> + * @mode: DRM display mode
>>>> + * @hdmi_output: HDMI output colorspace
>>>> + *
>>>> + * Return: 0 on success or a negative error code on failure.
>>>> + */
>>>> +int
>>>> +drm_hdmi_avi_infoframe_set_colorspace(struct hdmi_avi_infoframe *frame,
>>>> + const struct drm_display_mode *mode,
>>>> + enum hdmi_colorspace colorspace)
>>>> +{
>>>> + if (colorspace > HDMI_COLORSPACE_YUV420 ||
>>>> + colorspace < HDMI_COLORSPACE_RGB) {
>>>> + DRM_ERROR("Invalid color space type\n");
>>>> + return -EINVAL;
>>>> + }
>>> Seems overly defensive. I'd say that if someone insists on writing
>>> buggy code just let them do it.
>> :) yep can be done, you know, its a new implementation, don't want to
>> create unnecessary noise so being
>> a bit defensive :)
>>>> +
>>>> + frame->colorspace = colorspace;
>>>> + if (colorspace == HDMI_COLORSPACE_YUV420)
>>>> + frame->pixel_repeat = 0;
>>> Most VICs don't allow pixel repeat in 444/etc. either, and we don't
>>> protect against that. So this looks like pretty pointless check in
>>> this form.
>>>
>>> So IMO just drop this entire patch and just assign frame->colorspace in
>>> the driver.
>> Actually YCBCR420 section of spec specifically calls out for not
>> allowing repetition, also, when I tested this on a
>> HDMI 2.0 analyzer, if was giving a AVI IF failure on pixel_repeat not 0,
>> so IMHO it would be a good idea to keep
>> this and get the tests passing.
> That's just papering over bugs elsewhere. If we can't use pixel repeat
> with a specific mode, then we should have rejected that mode much earlier.
I dint get this point, HDMI 2.0 spec section 7.1 says "when YCBCR420
encoding is active, pixel repetition is not allowed" and
pixel repetition field should be set to = 0, in AVI IF. This seems to
be like - if you are displaying YCBCR420, set PR=0 regardless of
mode, isn't it ?
- Shashank
>> - Shashank
>>>> +
>>>> + return 0;
>>>> +}
>>>> +EXPORT_SYMBOL(drm_hdmi_avi_infoframe_set_colorspace);
>>>> +
>>>> +/**
>>>> * drm_hdmi_avi_infoframe_quant_range() - fill the HDMI AVI infoframe
>>>> * quantization range information
>>>> * @frame: HDMI AVI infoframe
>>>> diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
>>>> index aa58146..b79e0cb 100644
>>>> --- a/include/drm/drm_edid.h
>>>> +++ b/include/drm/drm_edid.h
>>>> @@ -332,6 +332,7 @@ struct cea_sad {
>>>> struct drm_encoder;
>>>> struct drm_connector;
>>>> struct drm_display_mode;
>>>> +enum drm_hdmi_output_type;
>>>>
>>>> void drm_edid_to_eld(struct drm_connector *connector, struct edid *edid);
>>>> int drm_edid_to_sad(struct edid *edid, struct cea_sad **sads);
>>>> @@ -354,6 +355,10 @@ drm_hdmi_avi_infoframe_from_display_mode(struct hdmi_avi_infoframe *frame,
>>>> const struct drm_display_mode *mode,
>>>> bool is_hdmi2_sink);
>>>> int
>>>> +drm_hdmi_avi_infoframe_set_colorspace(struct hdmi_avi_infoframe *frame,
>>>> + const struct drm_display_mode *mode,
>>>> + enum hdmi_colorspace colorspace);
>>>> +int
>>>> drm_hdmi_vendor_infoframe_from_display_mode(struct hdmi_vendor_infoframe *frame,
>>>> const struct drm_display_mode *mode);
>>>> void
>>>> --
>>>> 2.7.4
>>>>
>>>> _______________________________________________
>>>> dri-devel mailing list
>>>> dri-devel@lists.freedesktop.org
>>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-13 12:49 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:18 [PATCH 00/20] YCBCR 4:2:0 handling for LSPCON Shashank Sharma
2017-07-10 11:18 ` [PATCH 01/20] drm: handle HDMI 2.0 VICs in AVI info-frames Shashank Sharma
2017-07-10 11:18 ` [PATCH 02/20] drm/edid: complete CEA modedb(VIC 1-107) Shashank Sharma
2017-07-12 17:18 ` Ville Syrjälä
2017-07-13 5:38 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 03/20] drm/edid: parse sink information before CEA blocks Shashank Sharma
2017-07-10 11:18 ` [PATCH 04/20] drm/edid: cleanup patch for CEA extended-tag macro Shashank Sharma
2017-07-10 11:18 ` [PATCH 05/20] drm/edid: parse YCBCR420 videomodes from EDID Shashank Sharma
2017-07-10 11:18 ` [PATCH 06/20] drm: add helper to validate YCBCR420 modes Shashank Sharma
2017-07-12 17:18 ` Ville Syrjälä
2017-07-13 5:32 ` Sharma, Shashank
2017-07-13 12:31 ` Ville Syrjälä
2017-07-13 12:42 ` Sharma, Shashank
2017-07-13 13:00 ` Ville Syrjälä
2017-07-13 13:12 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 07/20] drm/edid: parse ycbcr 420 deep color information Shashank Sharma
2017-07-12 17:18 ` Ville Syrjälä
2017-07-13 5:33 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 08/20] drm: set output colorspace in AVI infoframe Shashank Sharma
2017-07-12 17:17 ` Ville Syrjälä
2017-07-13 5:07 ` Sharma, Shashank
2017-07-13 12:35 ` Ville Syrjälä
2017-07-13 12:49 ` Sharma, Shashank [this message]
2017-07-13 13:03 ` Ville Syrjälä
2017-07-13 13:15 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 09/20] drm: add helper functions for YCBCR420 handling Shashank Sharma
2017-07-12 17:17 ` Ville Syrjälä
2017-07-13 5:27 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 10/20] drm/i915: add config function for YCBCR420 outputs Shashank Sharma
2017-07-12 17:17 ` Ville Syrjälä
2017-07-13 5:26 ` Sharma, Shashank
2017-07-13 12:53 ` Ville Syrjälä
2017-07-13 13:01 ` Sharma, Shashank
2017-07-13 13:26 ` Ville Syrjälä
2017-07-13 13:35 ` Sharma, Shashank
2017-07-13 14:10 ` Ville Syrjälä
2017-07-13 14:17 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 11/20] drm/i915: prepare scaler for YCBCR420 modeset Shashank Sharma
2017-07-12 17:17 ` Ville Syrjälä
2017-07-13 5:21 ` Sharma, Shashank
2017-07-13 12:52 ` [Intel-gfx] " Ville Syrjälä
2017-07-13 12:57 ` Sharma, Shashank
2017-07-13 13:05 ` Ville Syrjälä
2017-07-10 11:18 ` [PATCH 12/20] drm/i915: prepare pipe for YCBCR420 output Shashank Sharma
2017-07-10 11:18 ` [PATCH 13/20] drm/i915: prepare csc unit " Shashank Sharma
2017-07-12 17:17 ` Ville Syrjälä
2017-07-13 5:14 ` Sharma, Shashank
2017-07-13 12:50 ` Ville Syrjälä
2017-07-13 12:53 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 14/20] drm/i915: set colorspace for YCBCR420 outputs Shashank Sharma
2017-07-10 11:18 ` [PATCH 15/20] drm/i915/glk: set HDMI 2.0 identifier Shashank Sharma
2017-07-10 11:18 ` [PATCH 16/20] drm: add function to read vendor OUI Shashank Sharma
2017-07-12 17:15 ` Ville Syrjälä
2017-07-13 5:04 ` Sharma, Shashank
2017-07-13 12:37 ` Ville Syrjälä
2017-07-13 12:50 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 17/20] drm/i915: check LSPCON " Shashank Sharma
2017-07-10 11:18 ` [PATCH 18/20] drm/i915: YCBCR 420 support for LSPCON Shashank Sharma
2017-07-12 17:15 ` Ville Syrjälä
2017-07-13 5:02 ` Sharma, Shashank
2017-07-13 13:13 ` Ville Syrjälä
2017-07-13 13:17 ` Sharma, Shashank
2017-07-10 11:18 ` [PATCH 19/20] drm/i915: Move AVI infoframe function to DDI layer Shashank Sharma
2017-07-12 17:15 ` Ville Syrjälä
2017-07-13 4:58 ` Sharma, Shashank
2017-07-13 13:10 ` Ville Syrjälä
2017-07-10 11:18 ` [PATCH 20/20] drm/i915: write AVI infoframes for LSPCON Shashank Sharma
2017-07-12 17:24 ` Ville Syrjälä
2017-07-13 5:41 ` Sharma, Shashank
2017-07-13 12:27 ` Ville Syrjälä
2017-07-13 12:39 ` Sharma, Shashank
2017-07-13 12:55 ` Ville Syrjälä
2017-07-13 13:10 ` Sharma, Shashank
2017-07-13 13:19 ` Ville Syrjälä
2017-07-13 13:21 ` 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=189e3351-3c58-9854-ab4b-e21938aea3ca@intel.com \
--to=shashank.sharma@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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