21 Apr
2009
21 Apr
'09
12:10 a.m.
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