i.MX8MM Device Tree Problem

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

i.MX8MM Device Tree Problem

4,691 Views
jack_huang1
Contributor III

/home/fsy/rel_imx_4.14.98_2.0.0_ga/linux-imx directory:

1. Modification:
 1) fsl-imx8mm-evk.dts
 Delete &i2c2 {the following:

        adv_bridge: adv7535@3d {
                compatible = "adi,adv7533";
                reg = <0x3d>;
                adi,addr-cec = <0x3b>;
                adi,dsi-lanes = <4>;
                status = "okay";

                port {
                        adv7535_from_dsim: endpoint {
                                remote-endpoint = <&dsim_to_adv7535>;
                        };
                };
        };

&mipi_dsi {
        status = "okay";

        port@1 {
                dsim_to_adv7535: endpoint {
                        remote-endpoint = <&adv7535_from_dsim>;
                };
        };
};


 2) Using the make menuconfig configuration, unselect the AV7511 encoder:
   Device Drivers->Graphics support->Display Interface Bridges->AV7511 encoder
2. Compile the make error message again

DTC     arch/arm64/boot/dts/freescale/fsl-imx8mm-evk-rm67191.dtb
Error: arch/arm64/boot/dts/freescale/fsl-imx8mm-evk-rm67191.dts:3.1-12 Label or path adv_bridge not found
FATAL ERROR: Syntax error parsing input tree
make[2]: *** [arch/arm64/boot/dts/freescale/fsl-imx8mm-evk-rm67191.dtb] Error 1
make[1]: *** [arch/arm64/boot/dts/freescale] Error 2

3.The contents of the error reporting office are as follows:

&adv_bridge {
        status = "disabled";
};

4.The comparison test shows that if the content of fsl-imx8mm-evk.dts is not deleted, it can compile normally, but rm67191 cannot mount the driver.

Question: Attached is the adjusted device tree file, please help to see why rm67191 could not be mounted and why the compilation failed.thank you

Labels (1)
Tags (1)
0 Kudos
6 Replies

3,556 Views
truman
Contributor I

hi,

i have the same problem to your question 4;

not only that, i can't mount other drivers either,like:led、pwm etc.

i realy hope you can help me!

this is a detailed description of my question :

https://community.nxp.com/t5/i-MX-Processors/i-MX8MM-uboot-can-t-load-driver/td-p/1291435

0 Kudos

4,289 Views
tanyid
Contributor I

Dear  igorpadykov:

   According to your suggestion, the following errors still appear:

[ 1.171478] Bus freq driver module loaded
[ 1.179377] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.185332] SuperH (H)SCI(F) driver initialized
[ 1.188295] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 30, base_baud = 5000000) is a IMX
[ 1.197045] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 31, base_baud = 5000000) is a IMX
[ 1.205652] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32, base_baud = 1500000) is a IMX
[ 1.216799] console [ttymxc1] enabled
[ 1.216799] console [ttymxc1] enabled
[ 1.221272] bootconsole [ec_imx6q0] disabled
[ 1.221272] bootconsole [ec_imx6q0] disabled
[ 1.230673] msm_serial: driver initialized
[ 1.244538] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.251174] [drm] No driver support for vblank timestamp query.
[ 1.257181] imx-drm display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[ 1.264851] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[ 1.271865] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[ 1.280142] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -19
[ 1.287846] ------------[ cut here ]------------
[ 1.292472] WARNING: CPU: 3 PID: 1 at drivers/gpu/drm/drm_bridge.c:155 drm_bridge_detach+0x50/0x60
[ 1.301428] Modules linked in:
[ 1.304487] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.14.98 #3
[ 1.310492] Hardware name: FSL i.MX8MM EVK board (DT)
[ 1.315542] task: ffff8000763b0000 task.stack: ffff000008078000
[ 1.321462] PC is at drm_bridge_detach+0x50/0x60
[ 1.326080] LR is at drm_encoder_cleanup+0x2c/0xa8
[ 1.330869] pc : [<ffff000008698258>] lr : [<ffff00000869ba64>] pstate: 60000145
[ 1.338263] sp : ffff00000807ba50
[ 1.341576] x29: ffff00000807ba50 x28: ffff800076a5f118
[ 1.346890] x27: 0000000000000039 x26: ffff80007681a400
[ 1.352203] x25: ffff8000767ba800 x24: 00000000ffffffed
[ 1.357517] x23: ffff000008f47980 x22: ffff000008f47000
[ 1.362830] x21: ff

0 Kudos

4,289 Views
rob_mclean
Contributor IV

I was getting a similar "WARNING:... drm_bridge_detach" error.  For me that warning went away when I figured out how to modify my device tree so my raydium,rm67191 panel driver got loaded.  

I don't see your panel driver getting loaded in the boot logs, I hope you were able to figure that out as well.

I'm using an i.MX8X not i.MX8M so that might not be your problem.

0 Kudos

4,289 Views
karangajjar
Senior Contributor II

Hi 克祥 黄 ,

You are seeing issue in compilation because:

fsl-imx8mm-evk-revb-rm67191.dts file includes fsl-imx8mm-evk-revb.dts which includes fsl-imx8mm-evk.dts. 

And fsl-imx8mm-evk-revb-rm67191.dts uses adv_bridge node to enable/disable. But adv_bridge node is define in fsl-imx8mm-evk.dts. That's why when you deleted the node it gave error from fsl-imx8mm-evk-revb-rm67191.dts.

Ideally, you should just disable the nodes you are not using. However, if you want to delete the node, then you should also delete from the files which are using that nodes(which includes fsl-imx8mm-evk.dts).

 

Also, you can just comment out the node if you want like below and try compiling:

adv_bridge: adv7535@3d {
/* compatible = "adi,adv7533";
reg = <0x3d>;
adi,addr-cec = <0x3b>;
adi,dsi-lanes = <4>;
status = "okay";

port {
adv7535_from_dsim: endpoint {
remote-endpoint = <&dsim_to_adv7535>;
};
};
*/};

Regards,
Karan Gajjar

0 Kudos

4,289 Views
igorpadykov
NXP Employee
NXP Employee

Hi 克祥 黄 

so what is purpose of these modifications, are you trying to disable adv7535 and

use only rm67191 ? For this one can use fsl-imx8mm-evk-rm67191.dts where adv_bridge is disabled

fsl-imx8mm-evk-rm67191.dts\freescale\dts\boot\arm64\arch - linux-imx - i.MX Linux kernel 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

4,289 Views
jack_huang1
Contributor III

Dear  igorpadykov:

          At present, rm67191 is adopted for external display, and adv7535 is not used, so the equipment in this part is being adjusted.I'll try it first, thanks.

0 Kudos