From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra114: Fix PLLX M, N, P init settings
Date: Fri, 20 Sep 2013 10:19:16 -0600 [thread overview]
Message-ID: <523C7584.2050902@wwwdotorg.org> (raw)
In-Reply-To: <1379680859-24121-1-git-send-email-treding@nvidia.com>
On 09/20/2013 06:40 AM, Thierry Reding wrote:
> From: Jimmy Zhang <jimmzhang@nvidia.com>
>
> The M, N and P width have been changed from Tegra30. The maximum value
> for N is limited to 255. So, the tegra_pll_x_table for Tegra114 should
> be set accordingly.
> diff --git a/arch/arm/cpu/arm720t/tegra-common/cpu.c b/arch/arm/cpu/arm720t/tegra-common/cpu.c
> struct clk_pll_table tegra_pll_x_table[TEGRA_SOC_CNT][CLOCK_OSC_FREQ_COUNT] = {
> /* T20: 1 GHz */
> - /* n, m, p, cpcon */
> + /*
> + * Field Bits Width
> + * n 17:8 10
> + * m 4:0 5
> + * p 22:20 3
It'd be nice to document the cpcon field size/position here too.
Nit: The various comments aren't consistent in their alignment (i.e.
width left/right justified, some bits values don't line up with others,
etc.)
> + */
> + /* n, m, p, cpcon */
> {{ 1000, 13, 0, 12}, /* OSC 13M */
> { 625, 12, 0, 8}, /* OSC 19.2M */
> { 1000, 12, 0, 12}, /* OSC 12M */
It might be useful to label all the table entries with the OSC frequency
that they apply to. But, perhaps that could be a different patch.
> - /* T114: 1.4 GHz */
> - {{ 862, 8, 0, 8},
> - { 583, 8, 0, 4},
> - { 696, 12, 0, 8},
> - { 700, 13, 0, 8},
> + /* T114: 1.9 GHz */
What does "1.9 GHz" mean here? Is that the/a max frequency the chip
supports? If so, it seems like a single value can't be accurate, since
max frequency is SKU-specific. As such, I wonder if it's even worth
including a number here?
I assume that the new table entries set up the same frequencies as what
was intended before; it's just that the old values were calculated
incorrectly. In other words, this patch is a bug-fix, not a change.
> + /*
> + * Field Bits Width
> + * n 15:8 8
> + * m 7:0 8
> + * p 23:20 4
> + */
> + {{ 108, 1, 1, 8}, /* actual: 702.0 MHz */
> + { 73, 1, 1, 4}, /* actual: 700.8 MHz */
> + { 116, 1, 1, 8}, /* actual: 696.0 MHz */
> + { 108, 2, 1, 8}, /* actual: 702.0 MHz */
next prev parent reply other threads:[~2013-09-20 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 12:40 [U-Boot] [PATCH] Tegra114: Fix PLLX M, N, P init settings Thierry Reding
2013-09-20 16:12 ` Tom Warren
2013-09-20 16:19 ` Stephen Warren [this message]
2013-09-20 16:33 ` 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=523C7584.2050902@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.