From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] OMAP3: Fix timer handling to 1ms and CONFIG_SYS_HZ to 1000
Date: Mon, 27 Apr 2009 17:07:01 +0200 [thread overview]
Message-ID: <49F5CA15.9080007@googlemail.com> (raw)
In-Reply-To: <20090426212427.GA32215@game.jcrosoft.org>
Dear Jean-Christophe,
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:29 Tue 21 Apr , Dirk Behme wrote:
>> From: Manikandan Pillai <mani.pillai@ti.com>
>> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
>> Signed-off-by: Manikandan Pillai <mani.pillai@ti.com>
>> ---
> as Request precedently switch to 12Mhz source clock or
As answered already in (unanswered)
http://lists.denx.de/pipermail/u-boot/2009-April/050078.html
switch to 12MHz will have a larger code and implementation impact
while we won't win anything compared to well tested 13MHz usage
http://lists.denx.de/pipermail/u-boot/2009-April/051258.html
> please specify the timer resolution & precision of your implementation and
> put in the commit message & code
It seems to me that you mix here OMAP1 and OMAP3 patches?
I remember about
http://lists.denx.de/pipermail/u-boot/2009-April/051271.html
which is regarding arm925/OMAP1 changes, not OMAP3 patch. I can't
remember anything similar regarding OMAP3 patch. And similar comment
for OMAP3 patch wouldn't make sense as
http://lists.denx.de/pipermail/u-boot/2009-April/051178.html
has clear info
+ * We run the counter with 13MHz, divided by 8, resulting in timer
+ * frequency of 1.625MHz. With 32bit counter register, counter
+ * overflows in ~44min
Dirk
next prev parent reply other threads:[~2009-04-27 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:29 [U-Boot] [PATCH v3] OMAP3: Fix timer handling to 1ms and CONFIG_SYS_HZ to 1000 Dirk Behme
2009-04-26 21:24 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-27 15:07 ` Dirk Behme [this message]
2009-04-30 21:56 ` Wolfgang Denk
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=49F5CA15.9080007@googlemail.com \
--to=dirk.behme@googlemail.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 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.