From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH][BUGFIX] Incorrect handling of AT91RM9200 timer overflow
Date: Tue, 22 Nov 2005 10:32:11 +0100 [thread overview]
Message-ID: <4382E59B.4090702@imc-berlin.de> (raw)
In-Reply-To: <fc.004c4e48003a7993004c4e48003a7993.3a79ba@rea.de>
Wolfgang,
> the AT91RM9200 timer functions are confusing apples with bananas.
>
> When the (16-bit) timer overflows, we have lost exactly 2^16 counts
> (or a multiple thereof, but we currently can't catch that situation),
> but get_timer_raw() instead adds the (unrelated) conversion factor
> to milliseconds, causing udelay() to potentially return too early.
>
> The patch below fixes this.
>
> Cheers
> Anders
>
> CHANGELOG:
> Fix incorrect handling of at91rm9200 timer overflow in get_timer_raw()
> Patch by Anders Larsen, 11 Nov 2005
>
> Signed-off-by: Anders Larsen <alarsen@rea.de>
Makes sense. Please apply.
--
Steven
prev parent reply other threads:[~2005-11-22 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 15:56 [U-Boot-Users] [PATCH][BUGFIX] Incorrect handling of AT91RM9200 timer overflow Anders Larsen
2005-11-22 9:32 ` Steven Scholz [this message]
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=4382E59B.4090702@imc-berlin.de \
--to=steven.scholz@imc-berlin.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