All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>,
	clinton.a.taylor@intel.com, dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: VSDB yCBCr420 Deep Color mode bit definitions
Date: Tue, 16 Oct 2018 16:53:56 +0300	[thread overview]
Message-ID: <874ldmknez.fsf@intel.com> (raw)
In-Reply-To: <374cf283-1f1a-4926-3194-b2e14079388a@intel.com>

On Mon, 15 Oct 2018, "Sharma, Shashank" <shashank.sharma@intel.com> wrote:
> Regards
>
> Shashank
>
>
> On 10/15/2018 4:39 PM, Jani Nikula wrote:
>> On Mon, 15 Oct 2018, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>>> On Fri, 05 Oct 2018, clinton.a.taylor@intel.com wrote:
>>>> From: Clint Taylor <clinton.a.taylor@intel.com>
>>>>
>>>> HDMI Forum VSDB YCBCR420 deep color capability bits are 2:0. Correct
>>>> definitions in the header for the mask to work correctly.
>>>>
>>>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107893
>>>> Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
>>> When posting fixes like this, please do git blame on the stuff you're
>>> fixing, and add Fixes: tag and a bunch of Cc's. It'll help us propagate
>>> the fix to stable kernels and get feedback from the authors and
>>> reviewers. 'dim fixes' will help you with this:
>>>
>>> $ dim fixes e6a9a2c3dc437
>>> Fixes: e6a9a2c3dc43 ("drm/edid: parse ycbcr 420 deep color information")
>>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> Cc: Jose Abreu <joabreu@synopsys.com>
>>> Cc: Shashank Sharma <shashank.sharma@intel.com>
>>> Cc: Gustavo Padovan <gustavo@padovan.org>
>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>> Cc: Sean Paul <sean@poorly.run>
>>> Cc: David Airlie <airlied@linux.ie>
>>> Cc: dri-devel@lists.freedesktop.org
>>> Cc: <stable@vger.kernel.org> # v4.14+
>>>
>>> Anyway this looks sane to me,
>>>
>>> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>>>
>>> but I'm wondering if there was some deeper meaning to the original |= in
>>> there.
> Honestly, I was considering new blocks in HDMI 2.1 spec for dc, and 
> parsing of those before this block, keeping |= required.
> But we can always do other way around, or will take care of it when we 
> add code for it.
> Just cross checked with the spec too,
>
> Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>

Pushed to drm-misc-fixes, thanks for the patch and review!

BR,
Jani.



>
> - Shashank
>
>> PS. It'll be useful to repost this Cc: intel-gfx just to get the CI as
>> we seem to be the only consumer of the stuff being fixed.
>>
>>>
>>> BR,
>>> Jani.
>>>
>>>
>>>> ---
>>>>   drivers/gpu/drm/drm_edid.c | 2 +-
>>>>   include/drm/drm_edid.h     | 6 +++---
>>>>   2 files changed, 4 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>>>> index 1e2b940..ff0bfc6 100644
>>>> --- a/drivers/gpu/drm/drm_edid.c
>>>> +++ b/drivers/gpu/drm/drm_edid.c
>>>> @@ -4282,7 +4282,7 @@ static void drm_parse_ycbcr420_deep_color_info(struct drm_connector *connector,
>>>>   	struct drm_hdmi_info *hdmi = &connector->display_info.hdmi;
>>>>   
>>>>   	dc_mask = db[7] & DRM_EDID_YCBCR420_DC_MASK;
>>>> -	hdmi->y420_dc_modes |= dc_mask;
>>>> +	hdmi->y420_dc_modes = dc_mask;
>>>>   }
>>>>   
>>>>   static void drm_parse_hdmi_forum_vsdb(struct drm_connector *connector,
>>>> diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
>>>> index b25d12e..e3c4048 100644
>>>> --- a/include/drm/drm_edid.h
>>>> +++ b/include/drm/drm_edid.h
>>>> @@ -214,9 +214,9 @@ struct detailed_timing {
>>>>   #define DRM_EDID_HDMI_DC_Y444             (1 << 3)
>>>>   
>>>>   /* YCBCR 420 deep color modes */
>>>> -#define DRM_EDID_YCBCR420_DC_48		  (1 << 6)
>>>> -#define DRM_EDID_YCBCR420_DC_36		  (1 << 5)
>>>> -#define DRM_EDID_YCBCR420_DC_30		  (1 << 4)
>>>> +#define DRM_EDID_YCBCR420_DC_48		  (1 << 2)
>>>> +#define DRM_EDID_YCBCR420_DC_36		  (1 << 1)
>>>> +#define DRM_EDID_YCBCR420_DC_30		  (1 << 0)
>>>>   #define DRM_EDID_YCBCR420_DC_MASK (DRM_EDID_YCBCR420_DC_48 | \
>>>>   				    DRM_EDID_YCBCR420_DC_36 | \
>>>>   				    DRM_EDID_YCBCR420_DC_30)
>

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-10-16 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 21:52 [PATCH] drm/edid: VSDB yCBCr420 Deep Color mode bit definitions clinton.a.taylor
2018-10-15 11:08 ` Jani Nikula
2018-10-15 11:09   ` Jani Nikula
2018-10-15 14:34     ` Sharma, Shashank
2018-10-16 13:53       ` Jani Nikula [this message]

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=874ldmknez.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=clinton.a.taylor@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 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.