New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 786440 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature
Gfx



Sign in to add a comment

CrOS: Surface HDCP version from kernel

Project Member Reported by seanpaul@chromium.org, Nov 17 2017

Issue description

We need to be able to differentiate between 1.4 and 1.2 (and possibly 2.2 once it becomes relevant).
 
Cc: jkardatzke@chromium.org
Cc: igo@chromium.org bhthompson@chromium.org
Owner: seanpaul@chromium.org
Status: Started (was: Available)
Going to take a crack at this today

Comment 3 by igo@chromium.org, Jan 24 2018

Is this relevant to ARC?
@c3: Yes, apparently android needs the HDCP version before it can present protected content. I've just cc'd you on the email thread.

Comment 5 by igo@chromium.org, Jan 24 2018

Cc: shihuis@chromium.org
Status: WontFix (was: Started)
Bringing some data over from the email thread:

HDMI, HDCP, and EDID versions map 1:1 up to 1.4. Since this is true, we already have the EDID version in chrome, which means we have the HDCP version in chrome. The EDID version is located in the 18th and 19th bytes of the EDID (major and minor, respectively).

According to tinskip@, DisplayPort only implements 1.3, so that case is also easy.

In light of this, we don't need to add anything further to kernel at this time. Once HDCP 2.2 comes along, we'll need to solve this problem, but deferring UAPI changes is almost always beneficial. Marking as fixed for now.

Sign in to add a comment