MLK-11408-2 imx: mx7d: Isolate 26 IP resources to domain 0 for A core

In current design, if any peripheral was assigned to both A7 and M4,
it will receive ipg_stop or ipg_wait when any of the 2 platforms
enter low power mode. We will have a risk that, if A7 enter wait,
M4 enter stop, peripheral will have chance to get ipg_stop and ipg_wait
asserted same time.

There are 26 peripherals impacted by this IC issue:
SIM2(sim2/emvsim2)
SIM1(sim1/emvsim1)
UART1/UART2/UART3/UART4/UART5/UART6/UART7
SAI1/SAI2/SAI3
WDOG1/WDOG2/WDOG3/WDOG4
GPT1/GPT2/GPT3/GPT4
PWM1/PWM2/PWM3/PWM4
ENET1/ENET2

Software Workaround:
The solution is set M4 to a different domain with A core.
So the peripherals are not shared by them. This way requires
the uboot implemented the RDC driver and set the 26 IPs above to domain 0 only.
CM4 image will set the M4 to domain 1 only.

This patch enables the CONFIG_MXC_RDC for mx7d SABRESD board and ARM2 boards, and
setup the 26 IP resources to domain 0.

Signed-off-by: Ye.Li <B37916@freescale.com>

1 files changed, 51 insertions, 0 deletions

diff --git a/arch/arm/cpu/armv7/mx7/soc.c b/arch/arm/cpu/armv7/mx7/soc.c
index e30493e2d4c..58621ce7d00 100644
--- a/arch/arm/cpu/armv7/mx7/soc.c
+++ b/arch/arm/cpu/armv7/mx7/soc.c
@@ -18,6 +18,10 @@
 #include <dm.h>
 #include <imx_thermal.h>
 #include <mxsfb.h>
+#ifdef CONFIG_MXC_RDC
+#include <asm/imx-common/rdc-sema.h>
+#include <asm/arch/imx-rdc.h>
+#endif
 #ifdef CONFIG_FSL_FASTBOOT
 #ifdef CONFIG_ANDROID_RECOVERY
 #include <recovery.h>
@@ -39,6 +43,50 @@ U_BOOT_DEVICE(imx7_thermal) = {
 };
 #endif
 
+#ifdef CONFIG_MXC_RDC
+static rdc_peri_cfg_t const resources[] = {
+    (RDC_PER_SIM1 | RDC_DOMAIN(0)),
+    (RDC_PER_SIM2 | RDC_DOMAIN(0)),
+    (RDC_PER_UART1 | RDC_DOMAIN(0)),
+    (RDC_PER_UART2 | RDC_DOMAIN(0)),
+    (RDC_PER_UART3 | RDC_DOMAIN(0)),
+    (RDC_PER_UART4 | RDC_DOMAIN(0)),
+    (RDC_PER_UART5 | RDC_DOMAIN(0)),
+    (RDC_PER_UART6 | RDC_DOMAIN(0)),
+    (RDC_PER_UART7 | RDC_DOMAIN(0)),
+    (RDC_PER_SAI1 | RDC_DOMAIN(0)),
+    (RDC_PER_SAI2 | RDC_DOMAIN(0)),
+    (RDC_PER_SAI3 | RDC_DOMAIN(0)),
+    (RDC_PER_WDOG1 | RDC_DOMAIN(0)),
+    (RDC_PER_WDOG2 | RDC_DOMAIN(0)),
+    (RDC_PER_WDOG3 | RDC_DOMAIN(0)),
+    (RDC_PER_WDOG4 | RDC_DOMAIN(0)),
+    (RDC_PER_GPT1 | RDC_DOMAIN(0)),
+    (RDC_PER_GPT2 | RDC_DOMAIN(0)),
+    (RDC_PER_GPT3 | RDC_DOMAIN(0)),
+    (RDC_PER_GPT4 | RDC_DOMAIN(0)),
+    (RDC_PER_PWM1 | RDC_DOMAIN(0)),
+    (RDC_PER_PWM2 | RDC_DOMAIN(0)),
+    (RDC_PER_PWM3 | RDC_DOMAIN(0)),
+    (RDC_PER_PWM4 | RDC_DOMAIN(0)),
+    (RDC_PER_ENET1 | RDC_DOMAIN(0)),
+    (RDC_PER_ENET2 | RDC_DOMAIN(0)),
+};
+
+static void isolate_resource(void)
+{
+    /* At default, all resources are in domain 0 - 3. Here we setup 
+     * some resources to domain 0 where M4 codes will move the M4
+     * out of this domain. Then M4 is not able to access them any longer.
+     * This is a workaround for ic issue. In current design, if any peripheral 
+     * was assigned to both A7 and M4, it will receive ipg_stop or ipg_wait 
+     * when any of the 2 platforms enter low power mode. So M4 sleep will cause
+     * some peripherals fail to work at A core side.
+     */
+    imx_rdc_setup_peripherals(resources, ARRAY_SIZE(resources));
+}
+#endif
+
 u32 get_cpu_rev(void)
 {
 	struct mxc_ccm_anatop_reg *ccm_anatop = (struct mxc_ccm_anatop_reg *)
@@ -167,6 +215,9 @@ int arch_cpu_init(void)
 
 	set_epdc_qos();
 
+#ifdef CONFIG_MXC_RDC
+    isolate_resource();
+#endif
 	return 0;
 }