HDCP Specification v1.1 Amendment for HDCP-GVIF Revision 1.0
2.3 HDCP-GVIF Port HDCP-GVIF Port device address is not required to be 0x74, because HDCP-GVIF Port is not I2C bus but GVIF embedded communication.
HDCP-GVIF port should support additional checksum code in order to detect transmission failures for HDCP-GVIF Port Combined-Format Byte Read.
HDCP-GVIF illustrated in
port does not support HDCP Port Link Fig.2-13 in HDCP specification rev1.1.
Integrity Message Read which This is because of considering
the time of accessing to Ri resister, loading Ri onto I2C buffer and sending read data to
2.4 Encryption Status Signaling HDCP-GVIF supports only EESS mode. Hence HDCP-GVIF devices do not need to determine which mode should be used by querying its Bcaps bit 1.1_FEATURES.
Data Encryption In case of GVIF-HDCP system, HDCP encryption is applied at the input to the GVIF encoder and decryption is applied at the output of the GVIF decoder rather than
M.D.S. encoder/decoder. When transmitting auxiliary data, same GVIF encoder/decoder is also used instead of TERC4 encoding used in HDMI.
Encryption/Decryption State Diagram
Video data period
Video data period for GVIF-HDCP is close to DVI rather than HDMI. There is no guard band. DE shall be asserted at the first pixel of the video data period and be de-asserted at the last pixel. Also preamble by CNTx signal is not required to indicate whether next period is video data period or data island period.
Data Island period
In the same manner as video data period, Data Island period has neither leading nor trailing guard band. AUX shall be asserted at the first pixel of the data island period, and be de-asserted at the last pixel. Auxiliary data or audio sample can be transmitted during this period and they are not packetized. Same GVIF encoding as Video Data Period is used during Data Island Period. Also preamble by CNTx signal is not required to indicate whether next period is video data period or data island period.
Digital Content Protection LLC