Hello
Qiang Li
I am now working on i.MX6DL with L3.0.35, and when we are playing video,we got a warning
"imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00080000", when the waring occured,
it appeared some color lines above the video view.(Frequency is very low).
Though I found many similar issues in the community(includes Re: imx6 android 4.3.1 IPU error when system start),
I did not find a solution for me.According to page 3174 of the IMX6SDLRM,there is discription for bit19 as below,
This bit indicates on the interrupt that is a result of an error during access to a synchronous display via DI0.
So could you tell me what kinds of error can cause the interrupt? And could you give me some advice to resolve
this problem?
I attached the kernel config file, u-boot config file and u-boot env settings
Thank you!
Best Regards,
ZongbiaoLiao
Original Attachment has been moved to: KernelConfig.txt.zip
Original Attachment has been moved to: UbootConfig.h.txt.zip
Original Attachment has been moved to: UbootEnvirment.txt.zip
Hi QiangLi,
in mxc_ipuv3_fb.c, I tried to remove the below coding in the function mxcfb_blank:
switch (blank){
case FB_BLANK_POWERDOWN:
case FB_BLANK_VSYNC_SUSPEND:
case FB_BLANK_HSYNC_SUSPEND:
case FB_BLANK_NORMAL:
if (mxc_fbi->dispdrv && mxc_fbi->dispdrv->drv->disable)
mxc_fbi->dispdrv->drv->disable(mxc_fbi->dispdrv);
ipu_disable_channel(mxc_fbi->ipu, mxc_fbi->ipu_ch, true);
if (mxc_fbi->ipu_di >= 0)
ipu_uninit_sync_panel(mxc_fbi->ipu, mxc_fbi->ipu_di);
ipu_uninit_channel(mxc_fbi->ipu, mxc_fbi->ipu_ch);
break;
case FB_BLANK_UNBLANK:
ret = mxcfb_set_par(info);
break;
}
I am expecting the screen to have no effect when i do blanking and unblanking as i remove the disable and enable of the IPU. However, when i do blanking, the screen will go black, and when i do unblanking, the screen will not return to the previous screen before blanking.
I think there is something else happening.. but i am not sure what is that. Can you advise?
Thank you.
Regards,
ZC
Except the mxcfb_blank() function, the blank/unblank event will also be handled in display device driver, such as ldb.c, ldb_fb_event().
So you code modification will impact the LVDS display initialization sequence.
Hi QiangLi,
Indeed it's related to the ldb_fb_event. i tried to disable the coding at the function and now the blanking doesn't take any effect. I will continue to probe into why is the error happening.
Regards,
ZC