From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott McNutt <smcnutt@psyent.com>
Date: Fri, 27 May 2011 09:07:18 -0400
Subject: [U-Boot] [RFC][Timer API] Revised Specification -
 Implementation details
In-Reply-To: <BANLkTik2zUcKc2P6Vq7jStyQ06NBzqq-Pg@mail.gmail.com>
References: <4DDE5548.3020906@gmail.com>
	<4DDE8639.3090909@comcast.net>	<BANLkTinWvY9b4QzeLNawF7MKT9z1zeMXyg@mail.gmail.com>	<20110527071355.5DA8014EF7F@gemini.denx.de>	<4DDF543D.6020506@gmail.com>	<20110527074832.5B98E1354FC@gemini.denx.de>	<BANLkTimB4YKkpk10gZkoRmLUYqbPxTHUKQ@mail.gmail.com>	<BANLkTik2SUm4Sm8aLjCrCmz+kcMGWgEzKw@mail.gmail.com>	<20110527112721.9023C101D7A@gemini.denx.de>
	<BANLkTik2zUcKc2P6Vq7jStyQ06NBzqq-Pg@mail.gmail.com>
Message-ID: <4DDFA206.5050101@psyent.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Graeme Russ wrote:
> Hi Wolfgang
> 
> On Friday, May 27, 2011, Wolfgang Denk <wd@denx.de> wrote:
>> Dear Graeme Russ,
>>
>> In message <BANLkTik2SUm4Sm8aLjCrCmz+kcMGWgEzKw@mail.gmail.com> you wrote:
>>> Besides, Nios can return an increment of 10 (presumably ms) between
>>> two immediately consecutive calls. This causes early timeouts in CFI
>>> driver
>> Now this in turn is a bug in the timer implementation that needs to be
>> fixed.

And this is what reset_timer() corrected.

> Agreed, but that is not something I can achieve - I don't want to hold
> up this whole show that we have all put so much effort into for the
> sake of one weak function

And I don't want to see something that currently works become broken
because we "improved" a feature ... simply because the resolution of
the timestamp is 10 msec rather than 1 msec.

And just to be clear. This is not a Nios issue. Currently, if the
timestamp is incremented via a fixed period interrupt, and the period
of the interrupt is longer that 1 msec, calls to get_timer() may
produce early timeouts ... regardless of platform.

--Scott