The AXI4-Stream carries active video data, driven by both the master and slave interfaces as seen in This Figure .
|
|
Blank periods, audio data, and ancillary data packets are not transferred through the video protocol over AXI4-Stream. All signals listed in Table: AXI4-Stream Video Protocol Input (Slave) Interface Signals and Table: AXI4-Stream Video Protocol Output (Master) Interface Signals are required for video over AXI4-Stream interfaces.
Table: AXI4-Stream Video Protocol Input (Slave) Interface Signals shows the interface signal names and functions for the input (slave) side connectors. To avoid naming collisions, the signal prefix s_axis_video should be appended to s_axis_video k , for IP with multiple AXI4-Stream input interfaces, where k is the index of the respective input AXI4-Stream; for example, axis_video_tvalid becomes s_axis_video0_tvalid for stream 0 and s_axis_video1_tvalid for stream 1.
1. InterfaceX Name mandates the top-level IP port names.
2. Video Specific Name should be short, descriptive signal names referring to AXI4-Stream ports that are to be used in HDL code, timing diagrams, and test benches.
Table: AXI4-Stream Video Protocol Output (Master) Interface Signals shows the interface signal names and functions for the output (master) side connectors. Similarly, for IP with multiple AXI4-Stream output interfaces, the signal prefix m_axis_video should be appended to m_axis_video k _ , where k is the index of the respective output AXI4-Stream; for example, axis_video_tvalid becomes m_axis_video0_tvalid for stream 0 and m_axis_video1_tvalid for stream 1.