Hi Paul, On Monday 30 September 2013 04:39 PM, Paul Walmsley wrote: > On Mon, 30 Sep 2013, Afzal Mohammed wrote: >>> The references to "wkup_pwrdm" on some of these clockdomains don't >>> look right to me. For example, this clockdomain is listed as being in >>> AM43XX_CM_WKUP_INST, but its enclosing powerdomain is listed as being in >>> AM43XX_PRM_WKUP_INST. Looks to me like it's best to have two different >>> wakeup powerdomains: one CM_WKUP, and one PRM_WKUP. >> >> On AM43x, prcm is a single block as in AM335x and is part of wakeup >> domain. This is different from OMAP4 that had separate prm and cm >> blocks. Script also generated the same output. > Why are there two different address offsets for CM_WKUP and PRM_WKUP? > From another patch in the series: > > +#define AM43XX_PRM_WKUP_INST 0x2000 > > ... > > +#define AM43XX_CM_WKUP_INST 0x2800 AM43XX_PRM_WKUP_INST and AM43XX_CM_WKUP_INST are offsets from PRCM_BASE. We don't have separate base address for PRM & CM. This is similar to as that in AM335x, where it is 0xD00 and 0x400 respectively (both from same base) as in prm33xx.h & cm33xx.h. Please note that AM43XX_PRM_PARTITION and AM43XX_CM_PARTITION both are '1'. PRCM register details from TRM (not yet public) is mentioned below. Regards Afzal PRCM Functional Registers The table below shows the base address and address space for the PRCM module instances. Table 2. PRCM Instance Summary ModuleName BaseAddress Size OCP_SOCKET_PRM 0x0000 256 Bytes PRM_MPU 0x0300 256 Bytes PRM_GFX 0x0400 256 Bytes PRM_RTC 0x0500 256 Bytes PRM_TAMPER 0x0600 256 Bytes PRM_CEFUSE 0x0700 256 Bytes PRM_PER 0x0800 6 KBytes PRM_WKUP 0x2000 2 KBytes CM_WKUP 0x2800 2 KBytes PRM_DEVICE 0x4000 256 Bytes CM_DEVICE 0x4100 256 Bytes CM_DPLL 0x4200 256 Bytes CM_MPU 0x8300 256 Bytes CM_GFX 0x8400 256 Bytes CM_RTC 0x8500 256 Bytes CM_TAMPER 0x8600 256 Bytes CM_CEFUSE 0x8700 256 Bytes CM_PER 0x8800 6 KBytes -- 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
