From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with i.MX31 processor
Date: Tue, 08 Jul 2008 17:14:35 +0200 [thread overview]
Message-ID: <4873845B.3020808@tqs.de> (raw)
In-Reply-To: <20080708143111.881B2242FF@gemini.denx.de>
Wolfgang Denk schrieb:
> In message <20080708093022.9272.4677.stgit@tq-sewsrv-4.tq-net.de> you wrote:
>> +/* Timer tick */
>> +#define CFG_HZ 32768
>
> CFG_HZ is a constant and has to be 1000.
I know, we had a discussion earlier about that issue (see "i.MX31:
question about CFG_HZ and CKIL" of 7th May). The situation is as follows:
The TQMA31, as well as the mx32ads use the General Purpose Timer 1,
which is feeded by a 32768 clock (possibly imx31_litekit and
imx31_phycore with 32000 Hz? I don't know.). The prescale divider can
only be an integer. 32768/1000 = non-integer.
The counter is just read. There are no real interrupts (I mention it,
because you wrote about this earlier).
The origin source code is from U-Boot V2, I suppose. Guennadi used it
for the mx31ads.
Currently, I see only one way to solve this:
1. Patch the common file cpu/arm1136/mx31/interrupts.c, function
interrupt_init(), so that the prescaler divides by 33.
Alternatively, also make the divider a board specific define.
2. Patch all mx31 board config header files with CFG_HZ 1000.
3. All mx31 boards have to be tested.
The following is impossible:
- changing the HW
- using an internal clock, because maximum is 1000 Hz * 4096 = 4096000
Hz (the maximum divider is 4096). All internal clocks are much higher.
Please for correction if I'm wrong.
What do you suggest to do and who does it?
And while we are at the timers:
The udelay function is the next problem:
udelay cannot go below 1/(32768 Hz) = 30.5 micros
The current function inserts a theoretical nop if the requested usec
value is below 1000. Therefore, IMHO, this timer is relatively
imprecise, because the resulting delay is below 1 microsecond.
IMHO, this all because of that slow input clock.
Kind regards,
Jens
next prev parent reply other threads:[~2008-07-08 15:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 9:33 [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with i.MX31 processor Jens Gehrlein
2008-07-08 10:32 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-08 12:09 ` Jens Gehrlein
2008-07-08 15:24 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-08 14:31 ` Wolfgang Denk
2008-07-08 15:14 ` Jens Gehrlein [this message]
2008-07-09 22:46 ` Wolfgang Denk
2008-07-10 6:22 ` Jens Gehrlein
2008-07-10 6:55 ` Wolfgang Denk
2008-07-10 7:29 ` [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new boardwith " Martin Krause
2008-07-10 20:54 ` [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with " Guennadi Liakhovetski
2008-07-10 8:20 ` Sascha Hauer
2008-07-10 8:17 ` Sascha Hauer
2008-07-10 8:49 ` Wolfgang Denk
2008-07-10 9:30 ` Sascha Hauer
2008-07-10 9:46 ` Wolfgang Denk
2008-07-10 10:16 ` Sascha Hauer
2008-07-08 22:55 ` Guennadi Liakhovetski
2008-07-08 23:16 ` Wolfgang Denk
2008-07-08 23:33 ` Guennadi Liakhovetski
2008-07-09 6:50 ` Wolfgang Denk
2008-07-09 6:32 ` Jens Gehrlein
2008-07-09 7:10 ` Wolfgang Denk
2008-07-09 12:09 ` Jerry Van Baren
[not found] <mailman.707077.1215511129.5026.u-boot-users@lists.sourceforge.net>
2008-07-08 11:33 ` Heiko Schocher
2008-07-08 11:38 ` Jens Gehrlein
2008-07-08 13:48 ` Heiko Schocher
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=4873845B.3020808@tqs.de \
--to=sew_s@tqs.de \
--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