[U-Boot] udelay/udelay_masked problems
Hi all, Is their a problem using udelay in board_init functions? When I do this on my at91, arm926ejs board, it seems to be in an endless loop. I thought this was a timer issue but I only have this problem with board init and not in the drivers. Does anyone have any ideas? Is timer_init a arch specific call or should it be board specific for arm?
Hi E Robertson,
2009/4/8 E Robertson e.robertson.svg@gmail.com:
Hi all, Is their a problem using udelay in board_init functions? When I do this on my at91, arm926ejs board, it seems to be in an endless loop. I thought this was a timer issue but I only have this problem with board init and not in the drivers. Does anyone have any ideas?
I guess the reason is:
start_armboot() in lib_arm/board.c invokes board_init() in board/atmel/<your at91 baord>/<your at92 board>.c before interrupt_init() in cpu/arm926ejs/interrupts.c which invokes timer_init() in cpu/arm926ejs/at91/timer.c.
That means timer_init() is called later than your board_init()
Is timer_init a arch specific call or should it be board specific for arm?
I have no idea either.
regards, Po-Yu chuang
On 11:52 Tue 07 Apr , E Robertson wrote:
Hi all, Is their a problem using udelay in board_init functions?
actually yes I'll send some patch to cleanuo the timer/interrupt init this week
When I do this on my at91, arm926ejs board, it seems to be in an endless loop. I thought this was a timer issue but I only have this problem with board init and not in the drivers. Does anyone have any ideas? Is timer_init a arch specific call or should it be board specific for arm?
no timer_init call is arm specific not board or even sub-arch
Best Regards, J.
participants (3)
-
E Robertson -
Jean-Christophe PLAGNIOL-VILLARD -
Po-Yu Chuang