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: Thu, 10 Jul 2008 08:22:27 +0200 [thread overview]
Message-ID: <4875AAA3.2040501@tqs.de> (raw)
In-Reply-To: <20080709224642.4951524304@gemini.denx.de>
Wolfgang Denk schrieb:
> In message <4873845B.3020808@tqs.de> you wrote:
>> 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.
>
> I think other architectures hav / had similar issues. See for example
> the MIPS fixes that were added some time ago.
I'll take a look.
>> 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.
>
> Sounds like a plan.
What do you mean?
It's just a proposal and I like to read comments from others, especially
those, who wrote this code.
>> 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.
>
> How is this handled in Linux? I don't think they would let this go
> through?
I don't no. Where can I start to have a look on? According to
experience, timer handling in Linux is much more complex.
Question: Why did you accept all the initial patches for
cpu/arm1136/mx31/interrupts.c and for the boards mx31ads, imx31_litekit,
imx31_phycore?
Kind regards,
Jens
next prev parent reply other threads:[~2008-07-10 6:22 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
2008-07-09 22:46 ` Wolfgang Denk
2008-07-10 6:22 ` Jens Gehrlein [this message]
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=4875AAA3.2040501@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