Memory
Y00 Y10 Y20
Y01 Y11 Y21
Y0M Y1M Y2M
YN0
YN1
YNM
Luma Only Client
Luma Chroma Client
Y00 Y10 Y20
Y01 Y11 Y21
Y0M Y1M Y2M
YN0
YN1
YNM
Y00 Y10 Y20
U00 U10 U20
V00 V10 V20
Y01 Y11 Y21
U01 U11 U21
V01 V11 V21
Y0M Y1M Y2M
U0M U1M U2M
V0M V1M V2M
YN0
UN0
VN0
YN1
UN1
VN1
YNM
UNM
VNM
Internal Modules
289
SPRUHI7A – December 2012 – Revised June 2016
Copyright © 2012–2016, Texas Instruments Incorporated
High-Definition Video Processing Subsystem (HDVPSS)
1.2.13.6 Data Formats
Each of the channels has a type of data that it can support based upon the client that it services. Also for
each channel, the data type will assume that data is packed in memory a certain way and will be
prevented to the client in the same manner to the client no matter what the format of the data in memory.
1.2.13.6.1 YUV Data Formats
The YUV formatted channels expect video data that is in YUV color space. The YUV data can be type is
for YUV data and it can support both interleaved data where Luma and Chroma are in the same data
buffer or it can support co-planar data where the Luma and Chroma are in separate data buffers. The
YUV channel also can be given a position to give a different start position for the client instead of the
default upper left hand corner of the frame. The storage format for YUV data depends on the data type
field. The data type must be set to a data type that the channel can support. All the clients that data are
provided too will either accept Luma Only, Chroma Only or Luma and Chroma in a parallel data bus.
1.2.13.6.1.1 Y 4:4:4 (Data Type 0)
The Y 4:4:4 data type is used for a co-planar 4:4:4 data. In this mode the data is assumed to be a single
byte with each pixel is packed in a line. If a 2D transfer of the data is used the VPDMA will assume this
data type is stored in an 8 bit container as described in the TILER specification. This data block should
have the width and height set to the desired frame size expected by the receiving client.
Figure 1-171. Y 4:4:4 (Data Type 0)
