The MIPI DSI TX Controller core consists of multiple layers defined in the MIPI DSI TX 2.0 specification, such as the lane management layer, low-level protocol, and pixel-to-byte conversion.
The DSI TX Controller core receives a stream of image data through an input stream interface. Based on the targeted display peripheral supported resolution and timing requirements, you must program the controller with the required timing values. The controller then generates packets fulfilling the required video timing markers based on different video transmit mode sequences. The core also supports sending short command packets during BLLP periods of video frames and sending long or short command packets when configured in the command mode. The following figure shows the MIPI DSI TX Controller sub-block details.
The core includes the following features:
- 1–4 lanes D-PHY support with a data rate of 2500 Mb/s per lane and 1–3 lanes C-PHY support with a data rate of 2250 Ms/s. This allows more bandwidth than that provided by a single lane. If you are trying to avoid high clock rates, the subsystem can expand the data path to multiple lanes and obtain approximately linear increases in peak bus bandwidth.
- Generates PPI transfers towards D-PHY/C-PHY with a continuous clock.
-
ECC and CRC calculation based on the algorithm specified in the
DSI Specification
. The correct interpretation
of the data identifier and word count values is vital to the packet structure.
ECC is calculated over the packet header.
To detect possible errors in transmission, a checksum is calculated over each data packet. The checksum is realized as a 16-bit CRC. The generator polynomial is x16+x12+x5+x0.
-
Command Queue, data queue, and command generation logic for
non-video packets. To send non-video packets to display peripheral, a command
queue is implemented to store the required command packets to be sent (for
example, Color mode on-off, Shutdown peripheral command, and so on).
- When in video mode, the controller finds enough time-slot available during the video blanking periods; these short commands are sent over the DSI link.
- When in command mode, the controller sends only the commands long/short programmed through the register. Video data is not sent in this mode.
- All three video modes supported (non-burst with sync pulses, non-burst with sync events, burst mode).
-
Pixel to byte conversion. The input video stream is expected to
be compliant with
AXI4-Stream Video IP and System Design Guide
(
UG934
)
recommendations. Based on data type, the incoming pixel stream is converted to
byte stream to match with the DSI requirements detailed in sec 8.8 of the
MIPI Alliance Standard for DSI specification
.
RGB component ordering, packed, and unpacked mechanisms differ between AXI4-Stream Video IP and System Design Guide ( UG934 ) and DSI Specification. Refer to AXI4-Stream Video IP and System Design Guide ( UG934 ) and DSI specifications for better understanding on component ordering, packed, unpacked styles, and so on.
The following figures show the incoming pixel stream ordering on an AXI4-Stream Video interface for different data types and pixels per clock combinations.
Figure 2. Single Pixel RGB888
Figure 3. Dual Pixels RGB888
Figure 4. Quad Pixels RGB888
Figure 5. Single Pixel RGB666 (Loosely, Packed)
Figure 6. Dual Pixels RGB666 (Loosely, Packed)
Figure 7. Quad Pixels RGB666 (Loosely, Packed)
Figure 8. Single Pixel RGB565
Figure 9. Dual Pixels RGB565
Figure 10. Quad Pixels RGB565
Figure 11. Single Pixel Compressed
Figure 12. Dual Pixel Compressed
Figure 13. Quad Pixel Compressed
- Register programmable EoTp generation support.
- Interrupt generation to indicate detection of underrun condition during pixel transfer and unsupported data types detected in the command queue.
- One horizontal scanline of active pixels is transferred as one single DSI packet.
- All mandatory uncompressed pixel formats 16 bpp (RGB565), 18 bpp (RGB666 packed), 18 bpp (RGB666 loosely packed), and 24 bpp (RGB888) are supported.
- Data types Packed 16-bit YUV 422, Loosely packed 20-bit YUV 422 and Packed 20-bit YUV 422 are supported for UltraScale+ and Versal devices.
- Core accepts compressed data type from GUI selection, where you are expected to pump in the compressed data. Core passes those streams of data without any conversion.