From mboxrd@z Thu Jan  1 00:00:00 1970
From: Graeme Russ <graeme.russ@gmail.com>
Date: Fri, 27 May 2011 17:33:39 +1000
Subject: [U-Boot] [RFC][Timer API] Revised Specification -
	Implementation details
In-Reply-To: <20110527071710.9423314EF7F@gemini.denx.de>
References: <4DDE5548.3020906@gmail.com>
	<20110526174901.5A34C15174E@gemini.denx.de>
	<BANLkTi=Nj09smJ+tTuE4p=rWFz=r9GBhwQ@mail.gmail.com>
	<20110527071710.9423314EF7F@gemini.denx.de>
Message-ID: <4DDF53D3.1060504@gmail.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

Hi Wolfgang,

On 27/05/11 17:17, Wolfgang Denk wrote:
> Dear Graeme Russ,
> 
> In message <BANLkTi=Nj09smJ+tTuE4p=rWFz=r9GBhwQ@mail.gmail.com> you wrote:
>>
>> I think we should - If CONFIG_SYS_HZ _MUST_ be 1000 anyway, what is the
>> point. Also, get_timer() utilisation as it stands for the most part already
>> assumes a 1ms time base. Maybe we should change get_timer() to
>> get_ms_timer() to avoid any ambiguity
> 
> No. At least not unless you also provide other get_<some unit>_timer()
> functions which we most likely will not do.

I think you will find most platforms will support get_us_timer() trivially.
Those that can't can use get_ms_timer() * 1000 (plus taking wrapping into
consideration)

Regards,

Graeme