DM388: Display Paths.

Kailash Negi

Intellectual 590 points

Part Number: DM388

HI All,

Following is my usecase, Capture and Tridisplay.

|-> display HDMI(1080P)

Capture |-> display HDCOMP(1080P)

| -> display DVO2(1080P)

HDMI is connected to Path SC2->VCOMP_MUX->CIG_NON_CONSTRAINED_OUTPUT->HDMI_BLEND.

HDDAC is connected to the Path BP0->HDCOMP_MUX->CIG_PIP_INPUT->CIG_PIP_OUTPUT->HDCOMP_BLEND.

DVO2 is conncted to the Path BPI->HDCOMP_MUX->CIG_PIP_INPUT->CIG_CONSTRAINED_OUTPUT->DVO2_BLEND.

Following is the display Controller MESH:

/* Display Controller Configuration */
/* To tie DVO2 and HDCOMP together refer following Mesh */
Vps_DcConfig gSystem_dctrlTriDisplayConfig = {
VPS_DC_USERSETTINGS, /* Use Case */
/* Edge information */
{
{VPS_DC_VCOMP_MUX, VPS_DC_VCOMP},
{VPS_DC_CIG_NON_CONSTRAINED_OUTPUT, VPS_DC_HDMI_BLEND},

{VPS_DC_BP0_INPUT_PATH, VPS_DC_HDCOMP_MUX} ,
{VPS_DC_HDCOMP_MUX, VPS_DC_CIG_PIP_INPUT} ,
{VPS_DC_CIG_PIP_OUTPUT, VPS_DC_HDCOMP_BLEND} ,

{VPS_DC_BP1_INPUT_PATH, VPS_DC_HDCOMP_MUX} ,
{VPS_DC_HDCOMP_MUX, VPS_DC_CIG_PIP_INPUT} ,

{VPS_DC_CIG_CONSTRAINED_OUTPUT, VPS_DC_HDCOMP_BLEND},

{VPS_DC_SEC1_INPUT_PATH, VPS_DC_SDVENC_MUX},
{VPS_DC_SDVENC_MUX, VPS_DC_SDVENC_BLEND},

{VPS_DC_GRPX0_INPUT_PATH, VPS_DC_HDMI_BLEND},
{VPS_DC_GRPX1_INPUT_PATH, VPS_DC_DVO2_BLEND},

{VPS_DC_GRPX1_INPUT_PATH, VPS_DC_HDCOMP_BLEND},
{VPS_DC_GRPX2_INPUT_PATH, VPS_DC_SDVENC_BLEND},

{VPS_DC_MAIN_INPUT_PATH, VPS_DC_VCOMP},
{VPS_DC_AUX_INPUT_PATH, VPS_DC_VCOMP_MUX},
},

16,
/* VENC information */
{
/* Mode information */
{
{VPS_DC_VENC_HDMI, {FVID2_STD_1080P_60}
}
, /* 1080p30 is mode
* is overwritten
* later inside
* System_displayCtrlInit
*/
{VPS_DC_VENC_HDCOMP, {FVID2_STD_1080P_60}
}, /* 1080p30 is mode
* is overwritten
* later inside
* System_displayCtrlInit
*/

{VPS_DC_VENC_DVO2, {FVID2_STD_1080P_60}
}, /* 1080p30 is mode
* is overwritten
* later inside
* System_displayCtrlInit
*/

{VPS_DC_VENC_SD, {FVID2_STD_NTSC}
}
}
,
(VPS_DC_VENC_DVO2 | VPS_DC_VENC_HDCOMP), /* Tied VENC bit
* mask */
4u /* Number of VENCs
*/
}
};

While running the above Usecase with the given display controller mesh.

Capture link is created and started successfully .
Display Link for Path SC2 created and started successfully.(This link is for HDMI).
Display Link for Path BP0 created and started successfully.(This link is for HDCOMP).
Dsiaply Link for Path BP1 created but Link start is Failed with the error "Assertion @line: 1119 in drivers/display/src/vps_dlm.c: (TRUE != client->state.isStarted): failed !!!"

Can you Please tell that what went wrong here?

Thanks

Kailash

over 6 years ago

0 Ravikiran HV over 6 years ago

Mastermind 8715 points

I can answer better, if I can look into the full source code.

However, please note that you have to start the SYNC's before the Sources of each link.

Please refer MCFW documents available in your IPNC release for more details

0 Brijesh Jadav over 6 years ago in reply to Ravikiran HV

TI__Guru**** 399120 points

Hi Kailash,

This is already being discussed at below link.

e2e.ti.com/.../630708

Rgds,
Brijesh

0 Kailash Negi over 6 years ago in reply to Brijesh Jadav

Intellectual 590 points

Hi Brijesh,

The link is pointing to this page itself.

Small correction
{VPS_DC_CIG_CONSTRAINED_OUTPUT, VPS_DC_DVO2_BLEND},

thanks
Kailash

0 Kailash Negi over 6 years ago in reply to Brijesh Jadav

Intellectual 590 points

Hi Ravikiran,

I am creating Capture link , then display HDMI link and Then Display HDCOMP link Then

Starting Display link HDMI then Display link HDCOMP. and at last Capture link.

Thanks

Kailash

0 Anuj Kumar Gupta over 6 years ago in reply to Kailash Negi

Genius 4030 points

Hi Kailash,

How you are connecting 3 display directly from capture link.
Since single vip instance of capture can give a max of 2 output queue.
And in the above reply of yours, where you are creating and starting display link for DVO2 for which you are facing error.

It would be better if you can share your usecase so that max of questions will be answered.
You can share it here or on my mail id anuj.gupta@pathpartnertech.com

0 Kailash Negi over 6 years ago in reply to Anuj Kumar Gupta

Intellectual 590 points

Hi Anuj,

I am using two output queue for from camera link , One is going directly to HDMI and other going to dup , from there its been sent two HDCOMP and DVO2 display links.

Camera-> | ->hdmi
|->dup ->|-> HDCOMP
|-> DVO2
link create and start seq
create cap link , create dup link, create HDMI link, create HDCOMP link, create DVO2 link.
start display links (HDMI ,HDCOMP,DVO2) then start Capture link.

I am facing some network issues i will share the usecase file when the issue is resolved.

Thanks
Kailash

Processors

Processors forum

DM388: Display Paths.