From 185c16609fed47333c84b4ccca2bc3480b377f19 Mon Sep 17 00:00:00 2001 From: Clark Wang <xiaoning.wang@nxp.com> Date: Fri, 1 Mar 2019 15:00:53 +0800 Subject: [PATCH] MLK-21017 ARM64: dts: disable CAN related regulators to fix CAN issue in M4 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) --- .../boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi | 16 ++++++++++++++++ .../dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi | 8 ++++++++ 2 files changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi b/arch/arm64/boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi index ec35ad5a83e33d..c35ca212d5f76f 100644 --- a/arch/arm64/boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi +++ b/arch/arm64/boot/dts/freescale/fsl-imx8qm-mek-rpmsg.dtsi @@ -68,6 +68,22 @@ status = "okay"; }; +®_can01_en { + status = "disabled"; +}; + +®_can2_en { + status = "disabled"; +}; + +®_can01_stby { + status = "disabled"; +}; + +®_can2_stby { + status = "disabled"; +}; + &intmux_cm41 { status = "disabled"; }; diff --git a/arch/arm64/boot/dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi b/arch/arm64/boot/dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi index 1d8f99294abf0b..27f9fea25fb397 100755 --- a/arch/arm64/boot/dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi +++ b/arch/arm64/boot/dts/freescale/fsl-imx8qxp-mek-rpmsg.dtsi @@ -183,6 +183,14 @@ status = "okay"; }; +®_can_en { + status = "disabled"; +}; + +®_can_stby { + status = "disabled"; +}; + &intmux_cm40 { status = "disabled"; }; -- GitLab