Lines Matching full:hdcp

1559  *	the appropriate means of protection (most often HDCP), and use the
1603  * HDCP Content Type:
1606  *	display content that userspace intended to display through HDCP
1610  *	"HDCP Type0" or "HDCP Type1".
1613  *	  - "HDCP Type0": DRM_MODE_HDCP_CONTENT_TYPE0 = 0
1614  *	  - "HDCP Type1": DRM_MODE_HDCP_CONTENT_TYPE1 = 1
1616  *	When kernel starts the HDCP authentication (see "Content Protection"
1617  *	for details), it uses the content type in "HDCP Content Type"
1618  *	for performing the HDCP authentication with the display sink.
1620  *	Please note in HDCP spec versions, a link can be authenticated with
1621  *	HDCP 2.2 for Content Type 0/Content Type 1. Where as a link can be
1629  *	either of HDCP spec versions 1.4 and 2.2. When HDCP2.2 is used for
1630  *	"HDCP Type 0", a HDCP 2.2 capable repeater in the downstream can send
1631  *	that content to a HDCP 1.4 authenticated HDCP sink (Type0 link).
1632  *	But if the content is classified as "HDCP Type 1", above mentioned
1633  *	HDCP 2.2 repeater wont send the content to the HDCP sink as it can't
1634  *	authenticate the HDCP1.4 capable sink for "HDCP Type 1".
1636  *	Please note userspace can be ignorant of the HDCP versions used by the
1637  *	kernel driver to achieve the "HDCP Content Type".
1642  *	Note that the HDCP Content Type property is introduced at HDCP 2.2, and
1643  *	defaults to type 0. It is only exposed by drivers supporting HDCP 2.2
1645  *	HDCP specs are defined content Type could be used for higher versions
1649  *	then kernel will disable the HDCP and re-enable with new type in the
1651  *	that link is HDCP authenticated and encrypted, for the transmission of
1652  *	the Type of stream mentioned at "HDCP Content Type".