From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, Nico Coesel <ncoesel@DEALogic.nl>
Subject: Re: FW: Alchemy power managment code.
Date: Fri, 28 Mar 2008 14:36:08 +0300 [thread overview]
Message-ID: <47ECD828.8090600@ru.mvista.com> (raw)
In-Reply-To: <20080327223134.GA26997@linux-mips.org>
Hello.
Ralf Baechle 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 ...
The Alchemy code doesn't even try to use CP0 counter when CONFIG_PM=y if
you look into arch/mips/au1000/common/time.c... or at least it didn't before
Atsushi removed do_fast_pm_gettimeoffset().
> Ralf
WBR, Sergei
next prev parent reply other threads:[~2008-03-28 11:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 16:16 FW: Alchemy power managment code Nico Coesel
2008-03-13 16:16 ` Nico Coesel
2008-03-13 16:45 ` Sergei Shtylyov
2008-03-24 14:23 ` Sergei Shtylyov
2008-03-24 14:31 ` Sergei Shtylyov
2008-03-27 22:31 ` Ralf Baechle
2008-03-28 11:36 ` Sergei Shtylyov [this message]
2008-03-28 13:32 ` Ralf Baechle
2008-03-28 14:25 ` Atsushi Nemoto
2008-03-28 15:14 ` Sergei Shtylyov
2008-03-26 16:31 ` FW: " Sergei Shtylyov
2008-03-27 22:32 ` Ralf Baechle
2008-03-28 11:39 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 13:46 Nico Coesel
2008-03-27 13:46 ` Nico Coesel
2008-03-27 16:41 ` Sergei Shtylyov
2008-03-27 22:33 ` Ralf Baechle
2008-03-28 8:21 Nico Coesel
2008-03-28 8:21 ` Nico Coesel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47ECD828.8090600@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ncoesel@DEALogic.nl \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.