53e108aa99
[Why] HDCP 2.2 uses type0 and type1 content type. This is passed to the receiver to stream the proper content. For example, in a MST case if the main device is HDCP2.2 capable but the secondary device is only 1.4 capabale we can use Type0 Type0 content: use HDCP 1.4 or HDCP2.2 type0 Type1 content: Only use HDCP 2.2 type1 [How] We use the "hdcp content type" property in drm. We use the disable_type1 flag in hdcp module to select the type based on the properties. For updating the property we use the same logic as 1.4, but now we consider content_type as well and update the property if the requirements are met Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> |
||
|---|---|---|
| .. | ||
| hdcp.c | ||
| hdcp.h | ||
| hdcp1_execution.c | ||
| hdcp1_transition.c | ||
| hdcp2_execution.c | ||
| hdcp2_transition.c | ||
| hdcp_ddc.c | ||
| hdcp_log.c | ||
| hdcp_log.h | ||
| hdcp_psp.c | ||
| hdcp_psp.h | ||
| Makefile | ||