Fix CONFIG_PRINTK_TIME
authorTony Lindgren <tony@atomide.com>
Thu, 15 Jun 2006 01:26:39 +0000 (18:26 -0700)
committerTony Lindgren <tony@atomide.com>
Thu, 15 Jun 2006 01:26:39 +0000 (18:26 -0700)
Fix CONFIG_PRINTK_TIME hangs on systems where sched_clock() does
not work before timer is initialized.

For example, on OMAP, symptoms of this problem include system
only booting with low level debug enabled when using 32KHz timer.

Signed-off-by: Tony Lindgren <tony@atomide.com>

No differences found