From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra: clk: always use find_best_divider() for periph clocks
Date: Mon, 13 May 2013 11:22:51 -0700 [thread overview]
Message-ID: <20130513182251.GA18968@badger> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37ACCAB0AB@HQMAIL04.nvidia.com>
On Mon, May 13, 2013 at 10:24:17AM -0700, Tom Warren wrote:
> Allen,
>
> > -----Original Message-----
> > From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
> > Sent: Friday, May 10, 2013 8:06 PM
> > To: Allen Martin
> > Cc: Tom Warren; Stephen Warren; U-Boot Mailing List
> > Subject: Re: [PATCH] Tegra: clk: always use find_best_divider() for periph
> > clocks
> >
> > On Fri, May 10, 2013 at 8:56 PM, Allen Martin <amartin@nvidia.com> wrote:
> > > When adjusting peripheral clocks always use find_best_divider()
> > > instead of clk_get_divider() even when a secondary divider is not
> > > available. In the case where is requested clock is too slow to be
> > > derived from the parent clock this allows a best effort to get close
> > > to the requested clock.
> > >
> > > This comes up for commands like "sf" where the user can pass a clock
> > > speed on the command line or "sspi" where the clock is hardcoded to
> > > 1MHz, but the Tegra114 SPI controller can't go that low.
>
> Did you test all other periphs and check their config'd clocks to make sure this doesn't affect anything else negatively? This proc is pretty universal (called by clock_start_periph_pll, which is used by MMC/I2C/USB/display drivers).
>
I tested a handful of peripherals on dalmore, but you're right this is
generic enough that it warrants a more thorough test scrubbing. I'll
try to hit all the peripherals I can across all chipsets and report
back.
-Allen
--
nvpublic
next prev parent reply other threads:[~2013-05-13 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 2:56 [U-Boot] [PATCH] Tegra: clk: always use find_best_divider() for periph clocks Allen Martin
2013-05-11 3:05 ` Simon Glass
2013-05-13 17:24 ` Tom Warren
2013-05-13 18:22 ` Allen Martin [this message]
2013-05-14 2:11 ` Allen Martin
2013-05-14 2:22 ` Tom Warren
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=20130513182251.GA18968@badger \
--to=amartin@nvidia.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