xref: /OK3568_Linux_fs/kernel/Documentation/driver-api/mei/hdcp.rst (revision 4882a59341e53eb6f0b4789bf948001014eff981)
1*4882a593Smuzhiyun.. SPDX-License-Identifier: GPL-2.0
2*4882a593Smuzhiyun
3*4882a593SmuzhiyunHDCP:
4*4882a593Smuzhiyun=====
5*4882a593Smuzhiyun
6*4882a593SmuzhiyunME FW as a security engine provides the capability for setting up
7*4882a593SmuzhiyunHDCP2.2 protocol negotiation between the Intel graphics device and
8*4882a593Smuzhiyunan HDC2.2 sink.
9*4882a593Smuzhiyun
10*4882a593SmuzhiyunME FW prepares HDCP2.2 negotiation parameters, signs and encrypts them
11*4882a593Smuzhiyunaccording the HDCP 2.2 spec. The Intel graphics sends the created blob
12*4882a593Smuzhiyunto the HDCP2.2 sink.
13*4882a593Smuzhiyun
14*4882a593SmuzhiyunSimilarly, the HDCP2.2 sink's response is transferred to ME FW
15*4882a593Smuzhiyunfor decryption and verification.
16*4882a593Smuzhiyun
17*4882a593SmuzhiyunOnce all the steps of HDCP2.2 negotiation are completed,
18*4882a593Smuzhiyunupon request ME FW will configure the port as authenticated and supply
19*4882a593Smuzhiyunthe HDCP encryption keys to Intel graphics hardware.
20*4882a593Smuzhiyun
21*4882a593Smuzhiyun
22*4882a593Smuzhiyunmei_hdcp driver
23*4882a593Smuzhiyun---------------
24*4882a593Smuzhiyun.. kernel-doc:: drivers/misc/mei/hdcp/mei_hdcp.c
25*4882a593Smuzhiyun    :doc: MEI_HDCP Client Driver
26*4882a593Smuzhiyun
27*4882a593Smuzhiyunmei_hdcp api
28*4882a593Smuzhiyun------------
29*4882a593Smuzhiyun
30*4882a593Smuzhiyun.. kernel-doc:: drivers/misc/mei/hdcp/mei_hdcp.c
31*4882a593Smuzhiyun    :functions:
32*4882a593Smuzhiyun
33