Re: [PATCH v4 07/11] ARM: OMAP2+: CM: AM43x clockdomain data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

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



- Paul
--
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




[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux