From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] PM: OMAP3: Make sure clk_disable_unused() order is correct
Date: Thu, 13 Nov 2008 05:55:31 -0800 [thread overview]
Message-ID: <87abc3loh8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1226482930-32017-1-git-send-email-tero.kristo@nokia.com> (Tero Kristo's message of "Wed\, 12 Nov 2008 11\:42\:10 +0200")
Tero Kristo <tero.kristo@nokia.com> writes:
> Current implementation will disable clocks in the order defined in clock34xx.h,
> at least DPLL4_M2X2 will hang in certain cases (and prevent retention / off)
> if clocks are not disabled in correct order. This patch makes sure the parent
> clocks will be active when disabling a clock.
>
> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
And, pulling into next PM branch.
Kevin
> ---
> arch/arm/mach-omap2/clock.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c
> index dbbc7c8..522ce6f 100644
> --- a/arch/arm/mach-omap2/clock.c
> +++ b/arch/arm/mach-omap2/clock.c
> @@ -1012,7 +1012,11 @@ void omap2_clk_disable_unused(struct clk *clk)
> return;
>
> printk(KERN_INFO "Disabling unused clock \"%s\"\n", clk->name);
> - _omap2_clk_disable(clk);
> + if (cpu_is_omap34xx()) {
> + omap2_clk_enable(clk);
> + omap2_clk_disable(clk);
> + } else
> + _omap2_clk_disable(clk);
> if (clk->clkdm.ptr != NULL)
> pwrdm_clkdm_state_switch(clk->clkdm.ptr);
> }
> --
> 1.5.4.3
>
> --
> 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:[~2008-11-13 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 9:42 [PATCH] PM: OMAP3: Make sure clk_disable_unused() order is correct Tero Kristo
2008-11-13 13:55 ` 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=87abc3loh8.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tero.kristo@nokia.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