IMX8MN MIPI DSI icn 6211 issue

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

IMX8MN MIPI DSI icn 6211 issue

1,221 次查看
topphysician
Contributor II

Hi,

I am working with imx8mn with kernel 6.1 where i try to use mipi-dsi with icn6211 bridge to rgb panel. The boot keeps crashing

In dts i added panel-connector and bridge in mipi-node:

	panel-connector {
		compatible = "custom,tl021wvc02", "simple-panel";

		port {
			panel_in: endpoint {
				remote-endpoint = <&bridge_out_dsi>;
			};
		};
	};
........
&mipi_dsi {
	status = "okay";
    bridge@0 {
		#address-cells = <1>;
        #size-cells = <0>;
        compatible = "chipone,icn6211"; // Update with correct compatible string if needed
        reg = <0>; 
		data-lanes = <4>;
		pinctrl-0 = <&pinctrl_mipi_bridge>;
        enable-gpios = <&gpio2 16 GPIO_ACTIVE_HIGH>;
		video-mode = <0>;
		status = "okay";

		port@1 {
			reg = <1>;
			bridge_out_dsi: endpoint {
				remote-endpoint = <&panel_in>;
			};
		};
    };
};

I also tried with port connecting bridge to mipi with no change.

The boot is stopped with crash, TRACE indicate custom prints.

Also appending whole boot.log here is tail of it:

[    1.805474][    T9] TRACE: drm_bridge_attach
[    1.831042][    T9] TRACE: sec_mipi_dsim_bind: bridge_bind_end
[    1.836885][    T9] imx-drm 32c00000.bus:display-subsystem: bound 32e10000.dsi_controller (ops imx_sec_dsim_ops)
[    1.848060][    T9] [drm] Initialized imx-drm 1.0.0 20120507 for 32c00000.bus:display-subsystem on minor 0
[    1.857785][    T9] TRACE: sec_mipi_dsim_connector_get_modes
[    1.857789][    T9] TRACE: drm_panel_get_modes panel: fffffffffffffdfb, connector: (____ptrval____)
[    1.872524][    T9] Unable to handle kernel paging request at virtual address fffffffffffffe0b
[    1.881145][    T9] Mem abort info:
[    1.884640][    T9]   ESR = 0x0000000096000004
[    1.889090][    T9]   EC = 0x25: DABT (current EL), IL = 32 bits
[    1.895104][    T9]   SET = 0, FnV = 0
[    1.898860][    T9]   EA = 0, S1PTW = 0
[    1.902702][    T9]   FSC = 0x04: level 0 translation fault
[    1.908281][    T9] Data abort info:
[    1.911861][    T9]   ISV = 0, ISS = 0x00000004
[    1.916397][    T9]   CM = 0, WnR = 0
[    1.920068][    T9] swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000004220d000
[    1.927471][    T9] [fffffffffffffe0b] pgd=0000000000000000, p4d=0000000000000000
[    1.934970][    T9] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
[    1.941934][    T9] Modules linked in:
[    1.945688][    T9] CPU: 2 PID: 9 Comm: kworker/u8:0 Not tainted 6.1.36-g01969ba8309e-dirty #227 0bddf5129db076e92bb5ef66eef20d492409d3fe
[    1.958037][    T9] Hardware name: Variscite VAR-SOM-MX8M-NANO on Symphony-Board (DT)
[    1.965869][    T9] Workqueue: events_unbound deferred_probe_work_func
[    1.972410][    T9] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    1.980069][    T9] pc : drm_panel_get_modes+0x38/0x70
[    1.985216][    T9] lr : drm_panel_get_modes+0x38/0x70
[    1.990359][    T9] sp : ffff8000080a36b0
[    1.994369][    T9] x29: ffff8000080a36b0 x28: ffff70b9c42e7180 x27: 0000000000000780
[    2.002207][    T9] x26: 0000000000000023 x25: ffffa10c81767d48 x24: ffff70b9c49ef800
[    2.010043][    T9] x23: 00000000fffffffd x22: ffff70b9c49f1420 x21: 0000000000000000
[    2.017880][    T9] x20: ffff70b9c49f10a0 x19: fffffffffffffdfb x18: ffffffffffffffff
[    2.025717][    T9] x17: 28203a726f746365 x16: 6e6e6f63202c6266 x15: 6466666666666666
[    2.033555][    T9] x14: 666666666666203a x13: ffffa10c814833d0 x12: 0000000000000387
[    2.041391][    T9] x11: 000000000000012d x10: ffffa10c814db3d0 x9 : ffffa10c814833d0
[    2.049228][    T9] x8 : 00000000ffffefff x7 : ffffa10c814db3d0 x6 : 80000000fffff000
[    2.057066][    T9] x5 : 000000000000bff4 x4 : 0000000000000000 x3 : 0000000000000000
[    2.064902][    T9] x2 : 0000000000000000 x1 : ffff70b9c00d8000 x0 : 000000000000004f
[    2.072740][    T9] Call trace:
[    2.075882][    T9]  drm_panel_get_modes+0x38/0x70
[    2.080678][    T9]  sec_mipi_dsim_connector_get_modes+0x30/0x4c
[    2.086692][    T9]  drm_helper_probe_single_connector_modes+0x1c4/0x510
[    2.093399][    T9]  drm_client_modeset_probe+0x1fc/0x1190
[    2.098889][    T9]  __drm_fb_helper_initial_config_and_unlock+0x44/0x540
[    2.105682][    T9]  drm_fbdev_client_hotplug+0x150/0x210
[    2.111085][    T9]  drm_fbdev_generic_setup+0xb4/0x194
[    2.116313][    T9]  imx_drm_bind+0x21c/0x270
[    2.120674][    T9]  try_to_bring_up_aggregate_device+0x1dc/0x2d0
[    2.126774][    T9]  __component_add+0xa4/0x190
[    2.131307][    T9]  component_add+0x14/0x20
[    2.135580][    T9]  lcdif_crtc_probe+0x4c/0xb0
[    2.140118][    T9]  platform_probe+0x68/0xc0
[    2.144480][    T9]  really_probe+0xc0/0x3dc
[    2.148753][    T9]  __driver_probe_device+0x7c/0x160
[    2.153807][    T9]  driver_probe_device+0x3c/0x110
[    2.158688][    T9]  __device_attach_driver+0xbc/0x160
[    2.163830][    T9]  bus_for_each_drv+0x7c/0xd4
[    2.168367][    T9]  __device_attach+0x9c/0x1c0
[    2.172900][    T9]  device_initial_probe+0x14/0x20
[    2.177782][    T9]  bus_probe_device+0x9c/0xa4
[    2.182316][    T9]  deferred_probe_work_func+0x94/0xe4
[    2.187544][    T9]  process_one_work+0x1d4/0x330
[    2.192255][    T9]  worker_thread+0x220/0x430
[    2.196703][    T9]  kthread+0x108/0x10c
[    2.200630][    T9]  ret_from_fork+0x10/0x20
[    2.204909][    T9] Code: b00088c0 aa1303e1 91246000 942172d5 (f9400a60) 
[    2.211699][    T9] ---[ end trace 0000000000000000 ]---

 

标记 (3)
0 项奖励
回复
2 回复数

1,163 次查看
topphysician
Contributor II

At the end I took bananapi icn6211 display: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20191003064527.15128-7-jagan@amarulasolu...
and changed it to fit my needs, where if the display will change: the uboot will change dts with different timings.

1,202 次查看
Chavira
NXP TechSupport
NXP TechSupport

Hi @topphysician!

Thank you for contacting NXP Support!

I tried with our iMX8MN EVK and configuring the MIPI DSI adding the device tree the icn6211 I didn't see any error like the error that you have.

I don't have the display but that error looks like any miss configuration in the drm driver or in the mipi_dsi node.

 

For this case I recommend to contacting Variscite support since we don't provide the software for the board that you are using.

 

Best Regards!

Chavira