This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 pipeline Priority thread

Hi,

I am using IPNC_RDK_DM36x_V5.1.0 on a DM365 board.

I understand that the threads are called in the same order as they are called in avserverMainthr.c file. And  is it based on the messages being sent using the OSA_tskSendMsg() function  or is it based on the function call that is being made in AvserverApi.c ?

OSA_tskSendMsg() function, sends message in following order.

Capture -> dei -> ldc -> Encrypt -> enf -> resize -> encode -> stream ->fd -> dmva -> Display 

AvServerApi.c function call is as shown below.

status |= VIDEO_captureCreate();
status |= VIDEO_resizeCreate();
status |= VIDEO_streamCreate();
status |= VIDEO_displayCreate();
status |= VIDEO_ldcCreate();
#ifdef YUV_MODE_INTERLACED
status |= VIDEO_deiCreate();
#endif
status |= VIDEO_vnfCreate();
status |= VIDEO_vsCreate();
status |= VIDEO_aewbCreate();
status |= VIDEO_fdCreate();
status |= VIDEO_dmvaCreate();
status |= VIDEO_encodeCreate();
status |= VIDEO_swosdCreate();
status |= VIDEO_encryptCreate();
status |= VIDEO_motionCreate();
status |= AUDIO_audioCreate();
status |= AUDIOPLAY_audioCreate();
status |= AVSERVER_mainCreate();

So if I have to bypass all the intermediate stages between my capture and display stream, should I just disable my other functions in the config file ?

I see that DisplayCopyrun() which is a function that copies the processed image at each stage into display buffer. I want to understand where exactly is Display stream getting executed ?

Please correct me if I'm wrong and suggest some good document that i can refer to understand the pipeline better.

Thanks!