| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | mdelay() from board_setup() [is default value for loops_per_jiffy way off?] |
| From: | Clem Taylor <clem.taylor@gmail.com> |
| Date: | Wed, 20 Apr 2005 13:50:10 -0400 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gCSxb683HoWwmCGfeE3ly8p1NeiISGcj9nHOFMJjWwzY4n1hNRph2Ko3zPbbBODOJJxd1mO5oBoNalMtI7YgHLYl3/Pg9VN8dma4R0RRqWpg3ZQEybVaQNEW5/N+09N1MRz7THoHtvK/0zH/j853ipZl/whoQ3aqEvjCYtMeylY= |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Reply-to: | Clem Taylor <clem.taylor@gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
Hi,
I'm working on a linux port for a custom Au1550 based board. Inside of
board_setup() I need to wait for some hardware to power up. So, I
called mdelay(), but it seems to wait for far too short a time. It
seems that loops_per_jiffy still has the default value (4096) in
board_setup(), the computed value is more like 245248. So, what is the
proper way to spin wait this early in the startup process? Also, isn't
the default value for loops_per_jiffy off by quite a bit? I'm running
the Au1550 at 492MHz, so that would make the default value good for a
~8MHz processor?
--Clem
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ieee754[sd]p_neg workaround, Ralf Baechle |
|---|---|
| Next by Date: | Re: mdelay() from board_setup() [is default value for loops_per_jiffy way off?], Pete Popov |
| Previous by Thread: | ieee754[sd]p_neg workaround, Atsushi Nemoto |
| Next by Thread: | Re: mdelay() from board_setup() [is default value for loops_per_jiffy way off?], Pete Popov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |