From: Kevin Hilman <khilman@deeprootsystems.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, dderrick@ti.com, r-woodruff2@ti.com
Subject: Re: [PATCH 01/04] OMAP3: PM: Disable PER DPLL idle before OFF, reduces OFF latency by 20ms
Date: Tue, 16 Jun 2009 07:21:24 -0700 [thread overview]
Message-ID: <87k53c5kez.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1245153154-1876-1-git-send-email-rnayak@ti.com> (Rajendra Nayak's message of "Tue\, 16 Jun 2009 17\:22\:31 +0530")
Rajendra Nayak <rnayak@ti.com> writes:
> If autoidle for DPLL4 is enabled in the stored scratchpad
> value of CM_AUTOIDLE_PLL then there is an added delay by
> the boot ROM when coming out of OFF mode.
> The patch disables this bitfield in the stored scratchpad value.
>
> This should significantly reduce CORE OFF latency and also
> bring down the threshold for CORE OFF, making OFF affordable
> even with smaller sleep times.
> This patch however does not optimize the C state threshold for
> CORE OFF states based on the new latency.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Please forgive the DPLL ignorance here, but I think a little more
verbose description is needed here, especially for those of use who
don't understand all the voodoo involved with DPLLs and ROM code
interaction.
>From this description, it's not clear what the resulting state of
DPLL4 will be and thus what the impact might be on power consumption.
IOW, Does this leave the DPLL in a locked, or is ROM code is doing a
software-programmed transition to low-power stop? or is there some
other automatic disable when PER goes to OFF?
Can you clarify and update the description. Thanks.
Kevin
> ---
> arch/arm/mach-omap2/control.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/control.c b/arch/arm/mach-omap2/control.c
> index c9407c0..a7159a9 100644
> --- a/arch/arm/mach-omap2/control.c
> +++ b/arch/arm/mach-omap2/control.c
> @@ -238,6 +238,13 @@ void omap3_save_scratchpad_contents(void)
> cm_read_mod_reg(PLL_MOD, CM_CLKEN);
> prcm_block_contents.cm_autoidle_pll =
> cm_read_mod_reg(PLL_MOD, OMAP3430_CM_AUTOIDLE_PLL);
> + /*
> + * ROM restore takes 20mS longer if PER idle is enabled before OFF.
> + * Clear feature before sleep. The origional idle state is
> + * restored by software as part of wake procedure.
> + */
> + prcm_block_contents.cm_autoidle_pll &= ~OMAP3430_AUTO_PERIPH_DPLL_MASK;
> +
> prcm_block_contents.cm_clksel1_pll =
> cm_read_mod_reg(PLL_MOD, OMAP3430_CM_CLKSEL1_PLL);
> prcm_block_contents.cm_clksel2_pll =
> --
> 1.5.4.7
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-16 14:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 11:52 [PATCH 01/04] OMAP3: PM: Disable PER DPLL idle before OFF, reduces OFF latency by 20ms Rajendra Nayak
2009-06-16 11:52 ` [PATCH 02/04] OMAP3: PM: Prevent AUTO_RET and AUTO_OFF being enabled simultaneously Rajendra Nayak
2009-06-16 11:52 ` [PATCH 03/04] OMAP3: PM: Fix I2C voltage levels send to T2 for different Power modes Rajendra Nayak
2009-06-16 11:52 ` [PATCH 04/04] OMAP3: PM: Update sleep/wakeup sequence and device grp associations Rajendra Nayak
2009-06-29 22:29 ` Kevin Hilman
2009-06-29 21:48 ` [PATCH 03/04] OMAP3: PM: Fix I2C voltage levels send to T2 for different Power modes Kevin Hilman
2009-06-16 12:39 ` [PATCH 02/04] OMAP3: PM: Prevent AUTO_RET and AUTO_OFF being enabled simultaneously Högander Jouni
2009-06-16 13:16 ` Nayak, Rajendra
2009-06-16 14:28 ` Kevin Hilman
[not found] ` <92CDD168D1E81F4F9D3839DC45903FC6536982E1@dlee03.ent.ti.com>
2009-06-16 17:28 ` Kevin Hilman
2009-06-17 16:52 ` Derrick, David
2009-06-17 6:27 ` Nayak, Rajendra
2009-06-29 21:45 ` Kevin Hilman
2009-06-16 12:52 ` [PATCH 01/04] OMAP3: PM: Disable PER DPLL idle before OFF, reduces OFF latency by 20ms Högander Jouni
2009-06-16 13:17 ` Nayak, Rajendra
2009-06-16 14:21 ` Kevin Hilman [this message]
2009-06-16 16:09 ` Derrick, David
2009-06-17 8:33 ` Paul Walmsley
[not found] <1245224794.6847.141.camel@ubuntu>
2009-06-17 9:50 ` Nayak, Rajendra
2009-06-17 10:26 ` Kalle Jokiniemi
2009-06-17 12:38 ` Nayak, Rajendra
2009-06-17 12:47 ` Kalle Jokiniemi
2009-06-17 13:01 ` Nayak, Rajendra
2009-06-29 18:58 ` Kevin Hilman
2009-06-30 5:58 ` Nayak, Rajendra
2009-06-30 22:24 ` Kevin Hilman
2009-06-30 22:32 ` Paul Walmsley
2009-07-01 5:39 ` Nayak, Rajendra
[not found] ` <87zlbov64k.fsf@deeprootsystems.com>
2009-07-01 14:28 ` Woodruff, Richard
2009-07-01 14:36 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k53c5kez.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=dderrick@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--cc=rnayak@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox