AUX Packets - 1.2 English - PG351

For HDMI, all data island packets consist of a 4-byte packet header and a 32 bytes of packet contents. In the following figure, the packet header contains 24 data bits (3 bytes) and 8 bits (1 byte) of BCH ECC parity.

In the following figure, packet body is made up of four subpackets; each subpacket includes 56 bits (7 bytes) of data and 8 bits (1 byte) of BCH ECC parity.

In the following table, the packet types are identified as handled by hardware and handled by software.

Tthe HDMI 2.1 RX Subsystem automatically drops the null packets. ACR, Audio Sample, HBR Audio, and 3D Audio routeto the audio interface. The remaining packets (packet types not highlighted in the previous table) route to the software for further processing by generating AUX packet interrupts.

In the HDMI 2.1 RX Subsystem driver, a generic API function allows you to retrieve aux packets.

XHdmiC_Aux *XV_HdmiRxSs1_GetAuxiliary(XV_HdmiRxSs1 *InstancePtr);

where,

• InstancePtr is a pointer to the HDMI 2.1 RX Subsystem instance.
• It returns a pointer to a data structure contains the complete AUX packet.

The driver defines the following AUX packet data structure:

typedef union {
    u32 Data;  
    u8 Byte[4]; 
} XHdmiC_AuxHeader;
typedef union {
    u32 Data[8];  
    u8 Byte[32];  
} XHdmiC_AuxData;
typedef struct {
  XHdmiC_AuxHeader Header; 
  XHdmiC_AuxData Data;
} XHdmiC_Aux;

The HDMI Common driver also defines API functions to parse important InfoFrame packets and general control packets so that this information is available for use in the user application software.

The following available parser APIs include:

void XV_HdmiC_ParseAVIInfoFrame(XHdmiC_Aux *AuxPtr, XHdmiC_AVI_InfoFrame *infoFramePtr);
void XV_HdmiC_ParseAudioInfoFrame(XHdmiC_Aux *AuxPtr, XHdmiC_AudioInfoFrame *AudIFPtr);
int XV_HdmiC_VSIF_ParsePacket(XHdmiC_Aux *AuxPtr, XHdmiC_VSIF *VSIFPtr);
void XV_HdmiC_ParseGCP(XHdmiC_Aux *AuxPtr, XHdmiC_GeneralControlPacket *GcpPtr);
void XV_HdmiC_ParseDRMIF(XHdmiC_Aux *AuxPtr, XHdmiC_DRMInfoFrame *DRMInfoFrame);

The parsed information is stored in data structures with respect to the packet type.

The driver does not parse other packet types. Instead, upon the AUX interrupt, you must retrieve those packets and process them in the application software. For example, if an HDMI source sends NTSC VBI Infoframe, upon receiving them by HDMI Subsystem, the NTSC VBI packet (both header and payload) is stored in the hardware FIFO, an AUX interrupt is generated. Then the application software reads out the AUX from the FIFO. By checking the packet header, the application knows that the packet is NTSC VBI. Then the application software must parse the payload data and handle it according to their system requirements.