The m_axis_video_tready signal can be asserted before, during or
after the cycle in which the AXI4-Stream Remapper core asserted
m_axis_video_tvalid. The assertion of
m_axis_video_tready might be dependent on the value of
m_axis_video_tvalid. A slave that can immediately accept data
qualified by m_axis_video_tvalid, should pre-assert its
m_axis_video_tready signal until data is received.
Alternatively, m_axis_video_tready can be registered and driven the
cycle following VALID assertion.
Recommended: To minimize latency, your custom core slave interface should
drive
READY independently, or pre-assert READY.