All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Jose Abreu <joabreu@synopsys.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 04/11] drm: parse ycbcr420 vcb block
Date: Wed, 19 Apr 2017 21:34:17 +0530	[thread overview]
Message-ID: <e2103a22-07d6-b75d-68bc-a0a0e8e80bee@intel.com> (raw)
In-Reply-To: <CACvgo52UeT+A4xnz0-2HVY-aquFgScoptOu99Wo2CU7=vuU3=w@mail.gmail.com>

Regards

Shashank


On 4/8/2017 11:13 PM, Emil Velikov wrote:
> Hi Shashank,
>
> On 7 April 2017 at 17:39, Shashank Sharma <shashank.sharma@intel.com> wrote:
>
>> +       u64 hdmi_420_cap_map = connector->display_info.hdmi.ycbcr420_vcb_map;
>>
>>          for (i = 0; i < len; i++) {
>>                  struct drm_display_mode *mode;
>>                  mode = drm_display_mode_from_vic_index(connector, db, len, i);
>>                  if (mode) {
>> +                       /*
>> +                        * ycbcr420 capability block contains a bitmap which
>> +                        * gives the index of such CEA modes in VDB, which can
>> +                        * support ycbcr420 sampling output also.
>> +                        * For example, if the bit 0 in bitmap is set,
>> +                        * first mode in VDB can support ycbcr420 output too.
>> +                        */
>> +                       if (hdmi_420_cap_map & (1 << i))
> Since map is u64 you really want to use something like (1ull << i)
> here. Otherwise you'll get a 32 bit value, regardless of i.
Thanks Emil, this was a good catch.
>
>> +       for (count = 0; count < map_len; count++)
>> +               map = (db[2 + count] << 8 * count) | map;
>> +
> The above issue is applicable here as well. With a small nitpick the
> whole thing will read
>
> map |= (u64)db[2 + count] << (8 * count);
Agree, thanks.
>
>> --- a/include/drm/drm_connector.h
>> +++ b/include/drm/drm_connector.h
>> @@ -136,6 +136,7 @@ struct drm_scdc {
>>   struct drm_hdmi_info {
>>          /** @scdc: sink's scdc support and capabilities */
>>          struct drm_scdc scdc;
>> +       u64 ycbcr420_vcb_map;
> As pointed by the kbuild robot - you really want to document the field.
Agree, will handle this in next patch set.
> Regards,
> Emil

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-04-19 16:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 16:39 [PATCH 00/11] HDMI YCBCR output handling in DRM layer Shashank Sharma
2017-04-07 16:39 ` [PATCH 01/11] drm: Add HDMI 2.0 VIC support for AVI info-frames Shashank Sharma
2017-04-10  9:47   ` Andrzej Hajda
2017-04-19 16:02     ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 02/11] drm/edid: Complete CEA modedb(VIC 1-107) Shashank Sharma
2017-05-08 16:22   ` Ville Syrjälä
2017-05-08 16:44     ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 03/11] drm: parse ycbcr 420 vdb block Shashank Sharma
2017-05-08 16:24   ` Ville Syrjälä
2017-05-08 16:41     ` Sharma, Shashank
2017-05-08 17:09       ` Ville Syrjälä
2017-05-09  8:34         ` Sharma, Shashank
2017-05-09 15:28           ` Ville Syrjälä
2017-05-10  5:01             ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 04/11] drm: parse ycbcr420 vcb block Shashank Sharma
2017-04-08 15:14   ` kbuild test robot
2017-04-08 17:43   ` Emil Velikov
2017-04-19 16:04     ` Sharma, Shashank [this message]
2017-05-08 16:58   ` Ville Syrjälä
2017-05-09  8:19     ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 05/11] drm: parse ycbcr 420 deep color information Shashank Sharma
2017-04-08 18:29   ` kbuild test robot
2017-04-07 16:39 ` [PATCH 06/11] drm: create hdmi output property Shashank Sharma
2017-04-08 20:53   ` kbuild test robot
2017-04-12  9:58   ` Jose Abreu
2017-04-19 15:50     ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 07/11] drm: set output colorspace in AVI infoframe Shashank Sharma
2017-04-12  9:49   ` Jose Abreu
2017-04-19 15:55     ` Sharma, Shashank
2017-04-07 16:39 ` [PATCH 08/11] drm/i915: handle ycbcr outputs Shashank Sharma
2017-04-07 16:39 ` [PATCH 09/11] drm/i915: handle csc for ycbcr HDMI output Shashank Sharma
2017-04-07 16:39 ` [PATCH 10/11] drm/i915: prepare ycbcr420 modeset Shashank Sharma
2017-04-07 16:39 ` [PATCH 11/11] drm/i915: set colorspace for ycbcr outputs Shashank Sharma
2017-04-07 17:41 ` ✓ Fi.CI.BAT: success for HDMI YCBCR output handling in DRM layer 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=e2103a22-07d6-b75d-68bc-a0a0e8e80bee@intel.com \
    --to=shashank.sharma@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joabreu@synopsys.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 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.