Part Number: PROCESSOR-SDK-J721E
Hi, TI team,
On our customer J721e target, flickers are observed in vehicle where all sensors are connected and load is high, and it looks like an underrun memory bandwidth when DSS assesses memory. On old J6 platform, we use to have similar issue, and then we enable mflag to resolve, and code lokos as below:
static void J6_set_pipeline_mflag(J6_dev_t *dev, int pipeId)
{
uint32_t volatile *buf_sz_reg;
uint32_t volatile *mflag_threshold_reg;
uint32_t fifosize;
switch (pipeId) {
case GFX_ID:
buf_sz_reg = DISPC_GFX_BUF_SIZE_STATUS;
mflag_threshold_reg = DISPC_GFX_MFLAG_THRESHOLD;
break;
case VID1_ID:
buf_sz_reg = DISPC_VID1_BUF_SIZE_STATUS;
mflag_threshold_reg = DISPC_VID1_MFLAG_THRESHOLD;
break;
case VID2_ID:
buf_sz_reg = DISPC_VID2_BUF_SIZE_STATUS;
mflag_threshold_reg = DISPC_VID2_MFLAG_THRESHOLD;
break;
case VID3_ID:
buf_sz_reg = DISPC_VID3_BUF_SIZE_STATUS;
mflag_threshold_reg = DISPC_VID3_MFLAG_THRESHOLD;
break;
default:
DC_ERROR("%s: wrong pipeline id %d", __FUNCTION__, pipeId);
return;
}
fifosize = *buf_sz_reg;
/* As per the simultaion team suggestion, below thesholds are set:
* HT = fifosize * 5/8;
* LT = fifosize * 4/8;
*/
*mflag_threshold_reg = (((fifosize*5)/8) << 16) | ((fifosize*4)/8);
*DISPC_GLOBAL_MFLAG_ATTRIBUTE = (0x1 << 2) | 0x2;
}
Looking into J7 TRM, I can find similar mflag usage, just wonder if J7 can same THRESHOLD configuration as J6, such as above "per the simultaion team suggestion". Thanks!
Dennis
