From: Kevin Hilman <khilman@deeprootsystems.com>
To: Vishwanath BS <vishwanath.bs@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 PM: Disable SR only during Device Retention/OFF
Date: Tue, 12 Jan 2010 10:40:40 -0800 [thread overview]
Message-ID: <874omrcgk7.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1262843526-22578-1-git-send-email-vishwanath.bs@ti.com> (Vishwanath BS's message of "Thu\, 7 Jan 2010 11\:22\:06 +0530")
Vishwanath BS <vishwanath.bs@ti.com> writes:
> Currently in omap_sram_idle function, SR is disabled whenever next state
> is retention/OFF w/o checking whether system can really enter retention/off.
> This patch adds another condition to disable SR. Basically FCLK register for
> Core and PER are checked before disabling SR. THis will give some more power
> savings in MP3 usecase (where Core enters retention where as PER does not).
>
> Tested OMAP3430 ZOOM2
>
> Signed-off-by: Vishwanath BS <Vishwanath.bs@ti.com>
I'm not going to take this one in it's current form as we had
discussions about this kind of thing earler when Tero had a series of
adding various fclk checks into the idle path.
I'm holding off on this patch until Tero's series is reviewed/merged.
He has added some functionality to check idleness of clockdomains and
powerdomains that could be used here.
Kevin
> ---
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 3868cdf..13c5dfb
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -479,6 +479,7 @@ void omap_sram_idle(void)
> int mpu_logic_state, mpu_mem_state, core_logic_state, core_mem_state;
> u32 sdrc_pwr = 0;
> int per_state_modified = 0;
> + u32 fclk_status;
>
> if (!_omap_sram_idle)
> return;
> @@ -545,15 +546,6 @@ void omap_sram_idle(void)
> if (pwrdm_read_pwrst(cam_pwrdm) == PWRDM_POWER_ON)
> omap2_clkdm_deny_idle(mpu_pwrdm->pwrdm_clkdms[0]);
>
> - /*
> - * Disable smartreflex before entering WFI.
> - * Only needed if we are going to enter retention or off.
> - */
> - if (mpu_next_state <= PWRDM_POWER_RET)
> - disable_smartreflex(SR1);
> - if (core_next_state <= PWRDM_POWER_RET)
> - disable_smartreflex(SR2);
> -
> /* CORE */
> if (core_next_state < PWRDM_POWER_ON) {
> omap_uart_prepare_idle(0, core_next_state & core_logic_state);
> @@ -600,6 +592,21 @@ void omap_sram_idle(void)
> omap3_intc_prepare_idle();
>
> /*
> + * Disable smartreflex before entering WFI.
> + * Only needed if we are going to enter retention or off.
> + */
> + fclk_status = cm_read_mod_reg(OMAP3430_PER_MOD, CM_FCLKEN) |
> + cm_read_mod_reg(CORE_MOD, CM_FCLKEN1) |
> + cm_read_mod_reg(CORE_MOD, OMAP3430ES2_CM_FCLKEN3);
> +
> + if (!fclk_status) {
> + if (mpu_next_state <= PWRDM_POWER_RET)
> + disable_smartreflex(SR1);
> + if (core_next_state <= PWRDM_POWER_RET)
> + disable_smartreflex(SR2);
> + }
> +
> + /*
> * On EMU/HS devices ROM code restores a SRDC value
> * from scratchpad which has automatic self refresh on timeout
> * of AUTO_CNT = 1 enabled. This takes care of errata 1.142.
> @@ -685,11 +692,12 @@ void omap_sram_idle(void)
> * Enable smartreflex after WFI. Only needed if we entered
> * retention or off
> */
> - if (mpu_next_state <= PWRDM_POWER_RET)
> - enable_smartreflex(SR1);
> - if (core_next_state <= PWRDM_POWER_RET)
> - enable_smartreflex(SR2);
> -
> + if (!fclk_status) {
> + if (mpu_next_state <= PWRDM_POWER_RET)
> + enable_smartreflex(SR1);
> + if (core_next_state <= PWRDM_POWER_RET)
> + enable_smartreflex(SR2);
> + }
> /* PER */
> if (per_next_state < PWRDM_POWER_ON) {
> if (per_next_state == PWRDM_POWER_OFF) {
> --
> 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
prev parent reply other threads:[~2010-01-12 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 5:52 [PATCH] OMAP3 PM: Disable SR only during Device Retention/OFF Vishwanath BS
2010-01-11 5:33 ` Sripathy, Vishwanath
2010-01-12 18:40 ` Kevin Hilman [this message]
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=874omrcgk7.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=vishwanath.bs@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