IMX8MN MIPI DSI ISSUE

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX8MN MIPI DSI ISSUE

1,007 Views
jack_huang1
Contributor III

Dears,

       The IMX8MN project encountered a problem related to MIPI DSI display, the specific problem is that the MIPI DSI output is connected to the MIPI to RGB chip (ICN6211), and the SDK version is LINUX SDK 5.10.72_2.0.0 (5.10.72 kernel), the following vblank wait timed was displayed during kernel initialization out exception. Attached is the completed dts configuration and log information, please check.

         

[    2.022054] panel-simple-dsi 32e10000.dsi_controller.0:

panel_simple_enable

[    3.037632] ------------[ cut here ]------------

[    3.037637] [CRTC:33:crtc-0] vblank wait timed out

[    3.037685] WARNING: CPU: 1 PID: 122 at

drivers/gpu/drm/drm_atomic_helper.c:1512

drm_atomic_helper_wait_for_vblanks.part.0+0x32c/0x340

[    3.037688] Modules linked in:

[    3.037698] CPU: 1 PID: 122 Comm: kworker/1:4 Not tainted

5.10.72-g56482195abaf-dirty #28

[    3.037701] Hardware name: NXP i.MX8MNano DDR4 EVK board (DT)

[    3.037711] Workqueue: events deferred_probe_work_func

[    3.037719] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)

[    3.037724] pc : drm_atomic_helper_wait_for_vblanks.part.0+0x32c/0x340

[    3.037729] lr : drm_atomic_helper_wait_for_vblanks.part.0+0x32c/0x340

[    3.037732] sp : ffff800012d0b470

[    3.037735] x29: ffff800012d0b490 x28: ffff8000119f1c50

[    3.037741] x27: 0000000000000000 x26: ffff8000119f1c28

[    3.037748] x25: 0000000000000001 x24: 0000000000000038

[    3.037755] x23: ffff0000044a0888 x22: ffff0000044a1000

[    3.037762] x21: ffff00000356ee00 x20: 0000000000000000

[    3.037767] x19: 0000000000000000 x18: ffff800012231c88

[    3.037774] x17: 0000000000000000 x16: 0000000000000000

[    3.037780] x15: 0000000000000030 x14: ffff800012518760

[    3.037786] x13: ffffffffffffffff x12: fffffffffffc460f

[    3.037794] x11: ffff800012231ca0 x10: fffffffffffe0000

[    3.037801] x9 : ffff800012d0b470 x8 : 6d69742074696177

[    3.037808] x7 : 206b6e616c627620 x6 : 00000000fffff12a

[    3.037815] x5 : 0000000000000000 x4 : 0000000000000000

[    3.037821] x3 : 00000000ffffffff x2 : 0000000000000000

[    3.037827] x1 : 0000000000000000 x0 : ffff000003770000

       

        Thank you!

        Best Regards!

       

0 Kudos
Reply
3 Replies

988 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @jack_huang1 

Please confirm that you uploaded two same dtsi files.

How does customer control the ICN6211 chip? with linux driver or external mcu?

0 Kudos
Reply

977 Views
jack_huang1
Contributor III

Dear Qmiller:

        In this scheme, the MIPI-DSI interface of IMX8MN is connected to the ICN6211, and the LINUX system is directly used.

         Sorry, I sent the wrong attachment.

         An attachment has been added again, please check. Thank you!

         Best Regards!

0 Kudos
Reply

956 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

If customer doesn't need use i2c to control the icn6211, they should only use mipi->panel, not add bridge type in dts.

If they need use i2c to control the icn6211, they should move bridge node into i2c node.

0 Kudos
Reply