From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ramalingam C Subject: Re: [PATCH v3 3/9] drm: Add Content Protection property Date: Thu, 7 Dec 2017 10:04:48 +0530 Message-ID: References: <20171205051513.8603-1-seanpaul@chromium.org> <20171205051513.8603-4-seanpaul@chromium.org> <423fd809-e7a4-f13b-a379-e1efb7f4c746@xs4all.nl> <0d921770-4645-8024-ad75-7041234ba7ff@intel.com> <3E576CE581B70742841A8994F80CE2EE4C914D69@BGSMSX104.gar.corp.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0473965964==" Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by gabe.freedesktop.org (Postfix) with ESMTPS id 2D4BF6E1D4 for ; Thu, 7 Dec 2017 04:38:20 +0000 (UTC) In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Sean Paul Cc: Hans Verkuil , dri-devel List-Id: dri-devel@lists.freedesktop.org This is a multi-part message in MIME format. --===============0473965964== Content-Type: multipart/alternative; boundary="------------1C0524336B3506BB8DBBE75F" Content-Language: en-US This is a multi-part message in MIME format. --------------1C0524336B3506BB8DBBE75F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On Wednesday 06 December 2017 09:56 PM, Sean Paul wrote: >>> I'd rather keep the property as-is and expose an HDCP version property >>> alongside it (or perhaps something more elaborate that includes bksv and the >>> downstream bksvs). The reason I prefer that is it will also cover the 1.2 vs 1.4 >>> difference that is a more immediate need. >> HDCP specification wants to differentiate 2.2 vs <2.2 as 2.2 is not a backward compatible. >> Why do we need to differentiate 1.2 and 1.4? Any use case? >> > Someone on the Chrome side asked me to surface the version, apparently > they care about 1.2 vs 1.4. > Sean, if you can get the reason for differentiating v1.2 and v1.4 at chrome, it will be educative info. - Thanks -Ram --------------1C0524336B3506BB8DBBE75F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit



On Wednesday 06 December 2017 09:56 PM, Sean Paul wrote:
I'd rather keep the property as-is and expose an HDCP version property
alongside it (or perhaps something more elaborate that includes bksv and the
downstream bksvs). The reason I prefer that is it will also cover the 1.2 vs 1.4
difference that is a more immediate need.

HDCP specification wants to differentiate 2.2 vs <2.2 as 2.2 is not a backward compatible.
Why do we need to differentiate 1.2 and 1.4? Any use case?


Someone on the Chrome side asked me to surface the version, apparently
they care about 1.2 vs 1.4.
Sean, if you can get the reason for differentiating v1.2 and v1.4 at chrome, it will be educative info. - Thanks

-Ram
--------------1C0524336B3506BB8DBBE75F-- --===============0473965964== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0473965964==--