Texas Instruments DM365, User Manual

Page: 104 / 131

API Reference
4-58
Notes:
‰ If the
outBuf
is cacahed, then the application needs to take care of
cacahe invalidating the data before doing any read/write operation. This
is because the input/output data is always read through DMA and not
CPU.
Example Usage:
‰ Configuring encoder
Assume slice size as 2MB row. Set encoder with below parameters:
IH264VENC_Params->sliceMode = 3
IH264VENC_Params->outputDataMode = 0
IH264VENC_Params->sliceFormat = 1
(assuming byte stream encoding)
IH264VENC_DynamicParams->sliceSize = 2
IH264VENC_InArgs->numOutputDataUnits = 1
This will enable encoder to produce slice of 2MB row and the Low
latency call back API will get called after 1 slice encode for data
exchange.
‰ Syncronization and Data Exchange
If the encoder is run in the above mode, the application will see the call
back function getting invoked after 1 slice encode. Application can use this
call back API for synchronization as well as data exchange. If the next
2MB row of data is put into DDR by capture driver, application can give the
next output slice pointer to the codec and release the call back. This will
make encoder proceed with further encoding. Please note that we use
output slice buffer pointer of encoded bitstream rather than input YUV to
control the encoder. The input YUV pointer is give at the start of process
call only as in the normal encoding.