From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ladislav Michl <ladis@linux-mips.org>
Date: Tue, 21 Apr 2009 00:10:18 +0200
Subject: [U-Boot] [PATCH] OMAP3: Fix timer handling to 1ms
	and	CONFIG_SYS_HZ to 1000.
In-Reply-To: <49ECB081.9050709@googlemail.com>
References: <1237285163-17307-1-git-send-email-dirk.behme@googlemail.com>
	<20090331202939.GI24923@game.jcrosoft.org>
	<20090401224353.E173783797DC@gemini.denx.de>
	<20090420190717.GA10270@localhost.localdomain>
	<49ECB081.9050709@googlemail.com>
Message-ID: <20090420221018.GA1853@localhost.localdomain>
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

On Mon, Apr 20, 2009 at 07:27:29PM +0200, Dirk Behme wrote:
> Ladislav Michl wrote:
>> After messing with OMAP1 timer code (which is copied again and again over
>> tree) I found such a reason. It is called 'void udelay(unsigned long usec)'
>> implementation and I hereby leaving its bugfixing as an excercise for a
>> reader [1]. 
>
> Would you mind giving some more details? This would avoid wasting time  
> to re-think about it (and maybe doing it wrong again) and would let us  
> better use the time for fixing the issues you see.

udelay is implemented using get_timer_masked and since that omap3 patch
limits timer resolution to 1ms, you get into trouble asking it to delay
100us as some drivers do.

	ladis