Each CM_REGION_TARGET is set to disabled at boot, so there is no need to disable the matching CM_GCR_REG explicitly. Signed-off-by: Niklas Svensson <niklass@xxxxxxxx> --- arch/mips/kernel/mips-cm.c | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/arch/mips/kernel/mips-cm.c b/arch/mips/kernel/mips-cm.c index f76f7a0..a4bbfd9 100644 --- a/arch/mips/kernel/mips-cm.c +++ b/arch/mips/kernel/mips-cm.c @@ -104,16 +104,6 @@ int mips_cm_probe(void) base_reg |= CM_GCR_BASE_CMDEFTGT_MEM; write_gcr_base(base_reg); - /* disable CM regions */ - write_gcr_reg0_base(CM_GCR_REGn_BASE_BASEADDR_MSK); - write_gcr_reg0_mask(CM_GCR_REGn_MASK_ADDRMASK_MSK); - write_gcr_reg1_base(CM_GCR_REGn_BASE_BASEADDR_MSK); - write_gcr_reg1_mask(CM_GCR_REGn_MASK_ADDRMASK_MSK); - write_gcr_reg2_base(CM_GCR_REGn_BASE_BASEADDR_MSK); - write_gcr_reg2_mask(CM_GCR_REGn_MASK_ADDRMASK_MSK); - write_gcr_reg3_base(CM_GCR_REGn_BASE_BASEADDR_MSK); - write_gcr_reg3_mask(CM_GCR_REGn_MASK_ADDRMASK_MSK); - /* probe for an L2-only sync region */ mips_cm_probe_l2sync(); -- 2.1.3
