From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] p2371: Remove hard-coded counter frequency
Date: Thu, 20 Aug 2015 09:33:03 -0600 [thread overview]
Message-ID: <55D5F32F.1030109@wwwdotorg.org> (raw)
In-Reply-To: <1440063743-22838-5-git-send-email-thierry.reding@gmail.com>
On 08/20/2015 03:42 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The counter frequency is derived from clk_m on Tegra, but that clock can
> be configured by the primary bootloader to run at the same frequency as
> the oscillator (38.4 MHz on Tegra210) or a divided down frequency (most
> typically 19.2 MHz). Remove the hard-coded frequency and allow the timer
> setup code to query the correct value at runtime.
> include/configs/p2371-0000.h | 2 --
Oh, there needs to be a patch for p2371-2180.h too. Perhaps just patch
all 4 boards in one go?
next prev parent reply other threads:[~2015-08-20 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 9:42 [U-Boot] [PATCH 1/6] armv8: Make COUNTER_FREQUENCY optional Thierry Reding
2015-08-20 9:42 ` [U-Boot] [PATCH 2/6] ARM: tegra: Implement clk_m Thierry Reding
2015-08-20 14:58 ` Stephen Warren
2015-08-20 16:20 ` Tom Warren
2015-08-27 17:08 ` Tom Warren
2015-08-20 9:42 ` [U-Boot] [PATCH 3/6] ARM: tegra: clk_m is the architected timer source clock Thierry Reding
2015-08-20 9:42 ` [U-Boot] [PATCH 4/6] e2220-1170: Remove hard-coded counter frequency Thierry Reding
2015-08-20 9:42 ` [U-Boot] [PATCH 5/6] p2371: " Thierry Reding
2015-08-20 15:33 ` Stephen Warren [this message]
2015-08-20 9:42 ` [U-Boot] [PATCH 6/6] p2571: " Thierry Reding
2015-08-20 15:32 ` [U-Boot] [PATCH 1/6] armv8: Make COUNTER_FREQUENCY optional Stephen 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=55D5F32F.1030109@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.