DisplayPort Intel® FPGA IP User Guide

ID 683273
Date 4/29/2022
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Give Feedback

5.8.7. Secondary Stream Interface

You can transmit the secondary stream data over the DisplayPort main link through the secondary stream (txN_ss) interface. This interface uses handshaking and back pressure to control packet delivery.
Note: The DisplayPort Intel® FPGA IP supports InfoFrame SDP versions 1.2 and 1.3 over the Main-Link. Use InfoFrame SDP version 1.2 to convey Audio InfoFrame control information, as specified in CEA-861-F and CEA-861.2. Other InfoFrame coding types, as specified in CEA-861-F, Table 5, and CEA-861.3, shall use InfoFrame SDP version 1.3. Refer to the DisplayPort Specification Section 2.2.5.1 for detailed definition.
Figure 21. Secondary Stream Input Data Format
Figure 22. Typical Secondary Stream PacketThis figure shows a typical secondary stream packet with a four-byte header (HB0, HB1, HB2 and HB3) and a 32-byte payload (DB0 … DB31).

The core calculates the associated parity bytes. The secondary stream interface uses the start-of-packet (SOP) and end-of-packet (EOP) to determine if the current input is a header or payload.

The ready latency is 1 clock cycle for the payload sub-packets. When core is ready, it sends the header forward. When the header is forwarded, the 16-byte payload (DB0 … DB15 and DB16 … DB31) must be available and the core must assert its associated valid signal on the next clock cycle when the output ready signal is high. The valid signal must remain low until the ready signal is high.

Figure 23. Typical Secondary Stream Packet Flow

The core supports only 16-byte and 32-byte payloads. Payloads that contain only the first 16 data bytes can assert the EOP on the second valid pulse to terminate the packet sequence. The core clocks in the data to the secondary stream interface through tx_ss_clk. tx_ss_clk is at the same phase and frequency as the main link lane 0 clock.

You can also use the secondary stream data packet to transport HDR metadata. CTA-861-G specification defines the HDR InfoFrame packet information as Packet Type, Version, data packets, and so on. The HDR metadata must follow InfoFrame SDP version 1.3 format defined in the VESA DisplayPort Standard version 1.4a.

For example, if the CTA-861-G specification-defined HDR InfoFrame type is 0x07, the VESA DisplayPort Standard version 1.4a-defined SDP InfoFrame Header Byte 1 as secondary-data packet type is 80h + Non-audio InfoFrame type value. The Header Byte 1 (HB1 in Figure 23) must be written to 87h.