The TDES954 MIPI CSI-2 protocol interface transmits the data identifier byte containing the values for the virtual channel ID (VC) and data type (DT) for the application specific payload data, as shown in Figure 7-11. The virtual channel ID is contained in the 2 MSBs of the data identifier byte and identify the data as directed to one of four virtual channels. The value of the data type is contained in the six LSBs of the data identifier byte. When partnered with a TSER953 serializer, the Data Type is passed through from the received CSI-2 packets. When partnered with a DVP Mode serializer, the received RAW mode data is converted to CSI-2 Tx packets with assigned data type and virtual channel ID and matches what is sent by the video source.

DVP format serializer inputs must have discrete sync signals. When interfacing with DVP Mode serializers, the TDES954 utilizes the HSYNC and VSYNC inputs to construct the MIPI CSI-2 Tx data packets. When paired with a DVP serializer, the TDES954 deserializer supports RAW8, RAW10 or RAW12 as well as formats which have the same pixel packing as RAW8, RAW10 or RAW12 such as YUV-422.

For each RX Port, registers define with which virtual channel and data type the RAW data context is associated:

• For V³Link Receiver port operating in RAW input mode connected to a DVP Mode serializer, register 0x70 (see Table 7-122) describes RAW10 Mode and 0x71 (see Table 7-123) RAW12 Mode.
• RAW1x_VC[7:6] field defines the associated virtual ID transported by the CSI-2 protocol from the sensor.
• RAW1x_ID[5:0] field defines the associated data type. The data type is a combination of the data type transported by the CSI-2 protocol.

Figure 7-11 CSI-2 Data Identifier Structure