From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: OMAP4+: Fix DPLL programming sequence
Date: Mon, 23 May 2016 10:24:53 -0500 [thread overview]
Message-ID: <574320C5.3040704@ti.com> (raw)
In-Reply-To: <1463990479-19403-1-git-send-email-lokeshvutla@ti.com>
On 05/23/2016 03:01 AM, Lokesh Vutla wrote:
> All the output clock parameters of a DPLL needs to be programmed before
> locking the DPLL. But it is being configured after locking the DPLL which
> could potentially bypass DPLL. So fixing this sequence.
>
> Reported-by: Richard Woodruff <r-woodruff2@ti.com>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> arch/arm/cpu/armv7/omap-common/clocks-common.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/cpu/armv7/omap-common/clocks-common.c b/arch/arm/cpu/armv7/omap-common/clocks-common.c
> index ef2ac98..2de9935 100644
> --- a/arch/arm/cpu/armv7/omap-common/clocks-common.c
> +++ b/arch/arm/cpu/armv7/omap-common/clocks-common.c
> @@ -236,6 +236,8 @@ static void do_setup_dpll(u32 const base, const struct dpll_params *params,
> /* Dpll locked with ideal values for nominal opps. */
> debug("\n %s Dpll already locked with ideal"
> "nominal opp values", dpll);
> +
> + bypass_dpll(base);
> goto setup_post_dividers;
> }
> }
> @@ -251,13 +253,13 @@ static void do_setup_dpll(u32 const base, const struct dpll_params *params,
>
> writel(temp, &dpll_regs->cm_clksel_dpll);
>
> +setup_post_dividers:
> + setup_post_dividers(base, params);
> +
> /* Lock */
> if (lock)
> do_lock_dpll(base);
>
> -setup_post_dividers:
> - setup_post_dividers(base, params);
> -
> /* Wait till the DPLL locks */
> if (lock)
> wait_for_lock(base);
>
LGTM
Reviewed-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2016-05-23 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 8:01 [U-Boot] [PATCH] ARM: OMAP4+: Fix DPLL programming sequence Lokesh Vutla
2016-05-23 15:24 ` Nishanth Menon [this message]
2016-05-30 18:06 ` [U-Boot] " Tom Rini
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=574320C5.3040704@ti.com \
--to=nm@ti.com \
--cc=u-boot@lists.denx.de \
/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