Bhawanpreet Lakha 53e108aa99 drm/amd/display: Handle hdcp2.2 type0/1 in dm ... [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>		2019-11-19 10:12:53 -05:00
..
color	drm/amd/display: remove set but not used variable 'min_content'	2019-11-19 10:12:51 -05:00
freesync	drm/amd/display: Add capability check for static ramp calc	2019-10-10 19:34:20 -05:00
hdcp	drm/amd/display: Handle hdcp2.2 type0/1 in dm	2019-11-19 10:12:53 -05:00
inc	drm/amd/display: Add execution and transition states for HDCP2.2	2019-11-19 10:12:53 -05:00
info_packet	drm/amd/display: set MSA MISC1 bit 6 while sending colorimetry in VSC SDP	2019-11-13 15:29:43 -05:00
power	drm/amd/display: set minimum abm backlight level	2019-10-03 09:10:57 -05:00
stats	drm/amd/display: remove redundant null pointer check before kfree	2018-09-26 21:09:12 -05:00
vmid	drm/amd/display: add missing mod_vmid destructor	2019-06-22 09:34:14 -05:00