linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: clock: Lock PLLs in the right sequence
Date: Thu, 08 Aug 2013 22:35:34 -0700	[thread overview]
Message-ID: <20130809053534.5348.29850@quantum> (raw)
In-Reply-To: <alpine.DEB.2.02.1308090345340.32157@utopia.booyaka.com>

Quoting Paul Walmsley (2013-08-08 20:47:02)
> Hi Mike,
> 
> On Thu, 8 Aug 2013, Mike Turquette wrote:
> 
> > Quoting Rajendra Nayak (2013-08-08 03:14:11)
> > > On OMAP4 we have clk_set_rate()s being done for a few
> > > DPLL clock nodes, as part of the clock init code, since
> > > the bootloaders no longer locks these DPLLs.
> > ...
> > > Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> > 
> > Taken into clk-next. Thanks for the fix. Besides the annoying prints is
> > there a functional regression fixed by this? If so I can take into
> > clk-fixes as needed.
> 
> It's best if I take this patch upstream.  That way, potential merge 
> conflicts are avoided, since I might have other changes to 
> arch/arm/mach-omap2/cclock44xx_data.c to send upstream at the same time.

No problem. I had not yet published it to clk-next so this causes no
issue.

Regards,
Mike

> 
> 
> - Paul

      reply	other threads:[~2013-08-09  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 10:14 [PATCH] ARM: OMAP4: clock: Lock PLLs in the right sequence Rajendra Nayak
2013-08-09  1:18 ` Mike Turquette
2013-08-09  3:47   ` Paul Walmsley
2013-08-09  5:35     ` Mike Turquette [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=20130809053534.5348.29850@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).