From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wolfgang Denk <wd@denx.de>
Date: Tue, 24 May 2011 16:19:50 +0200
Subject: [U-Boot] [RFC] Review of U-Boot timer API
In-Reply-To: <4DDBB29D.2050102@psyent.com>
References: <4DD7B245.5000008@gmail.com>
	<BANLkTineVAT1b_nWV8zPyfjsVnRz=6DhPg@mail.gmail.com>
	<201105240024.26511.vapier@gentoo.org>
	<BANLkTi=ayrqMGzjT-EvU3Hq3ZJbo=_8oOw@mail.gmail.com>
	<4DDB42B1.2010206@emk-elektronik.de>
	<BANLkTini5tCMFjaKkeJaehqQ0AokEv5_0g@mail.gmail.com>
	<4DDBB29D.2050102@psyent.com>
Message-ID: <20110524141950.2AB1CCF5DBF@gemini.denx.de>
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

Dear Scott McNutt,

In message <4DDBB29D.2050102@psyent.com> you wrote:
>
> Why must get_timer() be used to perform "meaningful time measurement?"

Excellent question!  It was never intended to be used as such.

Also, neither udelay() nor get_timer() make any warranties about
accuracy or precision. If they are a few percent off, that's perfectly
fine. Even if they are 10% off this is not a big problem anywhere.

> If all of this is about time measurement, why not start with your dream
> time measurement API, and go from there? And make it an optional
> feature.

D'acore.

> If the existing API, that has been used successfully for years,
> primarily as a mechanism for detecting a time-out, has issues,
> then let's resolve _those_ issues and avoid the "car-boat" ... the
> vehicle that floats like a car and handles like a boat. ;-)

:-)

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Sometimes a man will tell his bartender things he'll never tell his doctor.
	-- Dr. Phillip Boyce, "The Menagerie" ("The Cage"),
	   stardate unknown.