| To: | Sergei Shtylyov <sshtylyov@ru.mvista.com> |
|---|---|
| Subject: | Re: FW: Alchemy power managment code. |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 27 Mar 2008 22:31:35 +0000 |
| Cc: | linux-mips@linux-mips.org, Nico Coesel <ncoesel@DEALogic.nl> |
| In-reply-to: | <47E7BB4B.3080507@ru.mvista.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <19CA9E279FDA5246B7D7A1C91A4AF7F40EF804@dealogicserver.DEALogic.nl> <47E7B970.30105@ru.mvista.com> <47E7BB4B.3080507@ru.mvista.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Mon, Mar 24, 2008 at 05:31:39PM +0300, Sergei Shtylyov wrote: > > The TOY cpunter 0 clockevent driver is also need to be written for >> the recent kernel as CP0 timer stops ticking after wait insn is executed >> -- see arch/mips/au1000/common/time.c... > > And here's found another possible issue with Alchemy PM -- the CP0 > counter counts at unpredictable frequency in idle state (after executing > "wait"), so the MIPS clocksource will probably be unstable? Correct - and cevt-r4k won't be usable either. I guess that means you leave the user the choice between either these two or using wait. Not nice but ... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: FW: Alchemy power managment code., Ralf Baechle |
|---|---|
| Next by Date: | Re: FW: Alchemy power managment code., Ralf Baechle |
| Previous by Thread: | Re: FW: Alchemy power managment code., Sergei Shtylyov |
| Next by Thread: | Re: FW: Alchemy power managment code., Sergei Shtylyov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |