Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: > CPU0 and CPU1 clockdomain is at the offset of 0x18 from the LPRM base. > The header file has set it wrongly to 0x0. Offset 0x0 is for CPUx power > domain control register > > Fix the same. Has this also been updated in the autogen scripts? Benoit? Kevin > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> > --- > arch/arm/mach-omap2/prcm_mpu44xx.h | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/arm/mach-omap2/prcm_mpu44xx.h b/arch/arm/mach-omap2/prcm_mpu44xx.h > index 729a644..3300ff6 100644 > --- a/arch/arm/mach-omap2/prcm_mpu44xx.h > +++ b/arch/arm/mach-omap2/prcm_mpu44xx.h > @@ -38,8 +38,8 @@ > #define OMAP4430_PRCM_MPU_CPU1_INST 0x0800 > > /* PRCM_MPU clockdomain register offsets (from instance start) */ > -#define OMAP4430_PRCM_MPU_CPU0_MPU_CDOFFS 0x0000 > -#define OMAP4430_PRCM_MPU_CPU1_MPU_CDOFFS 0x0000 > +#define OMAP4430_PRCM_MPU_CPU0_MPU_CDOFFS 0x0018 > +#define OMAP4430_PRCM_MPU_CPU1_MPU_CDOFFS 0x0018 > > > /* -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
