> -----Original Message----- > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > Sent: Monday, February 07, 2011 2:12 AM > To: Santosh Shilimkar > Cc: linux-omap@xxxxxxxxxxxxxxx; khilman@xxxxxx; b-cousson@xxxxxx; > rnayak@xxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH v2 1/9] omap4: powerdomain: Add supported > INACTIVE power state > > Hi > > On Fri, 4 Feb 2011, Santosh Shilimkar wrote: > > > On OMAP4, one can explicitly program INACTIVE as the power state > of > > the logic area inside the power domain. Techincally PD state > programmed > > to ON and if all the clock domains within the PD are idled, is > equivalent > > tp PD programmed to INACTIVE and all the clock domains within the > PD are > > idled. There won't be any power difference in above two. > > > > This patch adds the support to allow power domain INACTIVE > programming > > which is supported on OMAP4. > > > > The powerdomain autogen script is updated accordingly. > > Continuing the discussion here: > > http://www.mail-archive.com/linux- > omap@xxxxxxxxxxxxxxx/msg43509.html > > 1. It appears that the OMAP4 powerdomain ON-ACTIVE state is a new > state > for OMAP4, and does not exist as such on previous chips (unless the > PRM_VOLTCTRL.AUTO_* bits are all disabled) > Actually it's not new state but more of convention change. ON-ACTIVE is like ON in OMAP3. > 2. It also appears that the OMAP4 powerdomain ON-INACTIVE state > is equivalent to the OMAP3 powerdomain ON state (again, assuming > that the > PRM_VOLTCTRL.AUTO_SLEEP bit is set on OMAP3). > This is correct. > Could you please comment on whether these statements are true or > false? > Just to summarise my undertsnaing of this here. On OMAP3 too, we had possibility of being in a one of the Two state when programmed to PD ON state. ON-ACTIVE or ON-INACTIVE. The PD status registers just says INACTIVE or ON based on the clodomains states within PD. On OMAP4, the difference is we do have a way to program the PD state explicitly as ON or INACTIVE. Regards, Santosh -- 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
