MLK-21017 ARM64: dts: disable CAN related regulators to fix CAN issue in M4
authorClark Wang <xiaoning.wang@nxp.com>
Fri, 1 Mar 2019 07:00:53 +0000 (15:00 +0800)
committerLeonard Crestez <leonard.crestez@nxp.com>
Wed, 17 Apr 2019 23:51:34 +0000 (02:51 +0300)
These CAN related regulators will be handled when kernel boots. However,
these regulators which aren't used by any devices will be disabled by the
regulator framework. So, the pins in these regulators will be non-active
status. This causes the CAN module cannot be used in M4 side.

So, disable these regualtors for 8QM/QXP, and let M4 handles these.

Suggested-by: Fugang Duan <fugang.duan@nxp.com>
Signed-off-by: Clark Wang <xiaoning.wang@nxp.com>
(cherry picked from commit 5c40db9cb2074c0c148d677acda55b0637c0c764)

arch/arm64/boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi
arch/arm64/boot/dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi

index ec35ad5..c35ca21 100644 (file)
        status = "okay";
 };
 
+&reg_can01_en {
+       status = "disabled";
+};
+
+&reg_can2_en {
+       status = "disabled";
+};
+
+&reg_can01_stby {
+       status = "disabled";
+};
+
+&reg_can2_stby {
+       status = "disabled";
+};
+
 &intmux_cm41 {
        status = "disabled";
 };
index 1d8f992..27f9fea 100755 (executable)
        status = "okay";
 };
 
+&reg_can_en {
+       status = "disabled";
+};
+
+&reg_can_stby {
+       status = "disabled";
+};
+
 &intmux_cm40 {
        status = "disabled";
 };