![background image](http://html1.mh-extra.com/html/texas-instruments/dm38x-davinci/dm38x-davinci_user-manual_1097067282.webp)
Internal Modules
282
SPRUHI7A – December 2012 – Revised June 2016
Copyright © 2012–2016, Texas Instruments Incorporated
High-Definition Video Processing Subsystem (HDVPSS)
1.2.13.5.1.1.2 Single YUV Color Separate
If the port is configured to be used as sending out color separated YUV data then the channels that must
be used are VIPX_PORTY_LUMA and VIPX_PORTY_CHROMA for the luma and chroma components
respectively. The data type can be either 420 or 422 color separate in this case.
1.2.13.5.1.1.3 Dual YUV Interleaved
If the port is configured to be used to send out 422 interleaved data from a non-multiplexed source then
the channels that must be used are VIPX_PORTY_LUMA or VIPX_PORTY_CHROMA depending on if the
data stream is connected to the luma or chroma port. The data type must be 422 interleaved in this case.
1.2.13.5.1.1.4 Single RGB Stream
If the port is configured to be used to send out RGB stream then the channel VIPX_PORTY_RGB must be
used. The incoming data is then assumed to be RGB 888 data and this is combined with the Background
Color Alpha register field to make ARGB8888 data that will then be sent out based on the data type. If the
data type uses less then the full 8 bits the lower bits are dropped and just the upper bits are sent to get
the correct data format.
1.2.13.5.1.2 De-Interlacers (DEIs)
The DEIs have two areas that require special handling in setting up the descriptors. The first is with the
line buffers. The line buffer must be set to match the mode that the chroma upsampler and the DEI expect
to receive for chroma and luma respectively. Refer to the Chroma Upsampler specification for the settings
for the chroma client. The luma client should use the same settings for the chroma assuming that the data
type is 422. The line buffer mode is set by the CSTAT register for the client. This value is not shadowed
and must be set before the descriptor is loaded and can not be changed until the client has finished. This
can be accomplished by using a Sync on Client Not Active control descriptor prior to a configuration
descriptor to change the line mode. The video clients also must have the 1D descriptor field set to 1 if
compression and decompression is used for the field data. Also, if the compression and decompression
are set then the write channel descriptors must also generate the next inbound descriptor as this is the
only way to know the size of the outbound data that will be the inbound data for the next frame.
1.2.13.5.1.3 Transcode Paths
The transcode paths must set the chroma line buffer to match the chroma upsampler in the transcode
path. Refer to the Chroma Upsampler specification for the settings for the chroma client. The line buffer
mode is set by the CSTAT register for the client. This value is not shadowed and must be set before the
descriptor is loaded and can not be changed until the client has finished. This can be accomplished by
using a Sync on Client Not Active control descriptor prior to a configuration descriptor to change the line
mode.
1.2.13.5.1.4 Noise Filter (NF)
The noise filter clients break the frame into 32 by 32 tiles for 422 data and 420 Luma data. The noise filter
clients break 420 chroma data into 32x16 tiles. The incoming 422 frame should be evenly divisible by 32
by 32. The outgoing frame buffers should leave enough space for a frame that is evenly divisible by 32 by
32 for luma and 32 by 16 for chroma.
1.2.13.5.1.5 Graphics
The graphics ports in this device are tightly coupled with the VPDMA clients that service them. Each
graphics port expects a list of data descriptors to describe each region that make up the frame.