From: Kenneth Johansson <kenneth@southpole.se>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Li Tao-B22598 <B22598@freescale.com>
Subject: Re: Question about e300 core decrementer interrupt
Date: Thu, 10 Sep 2009 11:09:54 +0200 [thread overview]
Message-ID: <1252573794.10293.13.camel@localhost> (raw)
In-Reply-To: <20090909184343.GC8215@b07421-ec1.am.freescale.net>
On Wed, 2009-09-09 at 13:43 -0500, Scott Wood wrote:
> On Wed, Sep 09, 2009 at 01:16:07PM +0200, Kenneth Johansson wrote:
> > On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote:
> > > Dear all,
> > >
> > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c4
> > > core. When I make the e300c4 core into sleep mode, it will return to
> > > full power mode when the“decrementer interrupt” occurred.
> > >
> > > But in the e300 core reference manual said that the “decrementer
> > > interrupt”have no effect when e300 core in sleep mode, because the
> > > time
> > > base and decrementer are disabled while the core is in sleep mode.
> > > Can anybody explain about this procedure ?
>
> I'm not specifically familiar with MPC5121, but I'll answer from the
> perspective of MPC83xx which has a similar core:
>
> The decrementer stops ticking when the core goes to sleep. However, if a
> decrementer was already pending (but masked with MSR[EE]) before you
> enter sleep mode, it will cause a wakeup.
>
> To avoid this, the decrementer is set to a very large value prior to and
> after disabling interrupts. See generic_suspend_disable_irqs() in
> arch/powerpc/kernel/time.c. Is this not happening for you? Which kernel
> version are you using, and what mechanism are you using to go to sleep?
>
> > I'm a bit irritated that it's not as the "solution" can mean hardware
> > changes an thus it's potentially expensive.
>
> What sort of hardware changes?
I don't want to spread missinformation but this procedure has helped on
the ads5121 rev3 and two custom boards.
the gpio 28,29,30 needs to be low and gpio31 needs to be hi. regardless
of what is used as wakeup source when the device enters deep sleep
otherwise you end up in some sort of meta state where you might not wake
up on anything and you have this 42 second auto wakeup from the
decrementer.
Other weired states has also been observed. the PMC module is a bit
tempremental in this chip.
next prev parent reply other threads:[~2009-09-10 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 5:48 Question about e300 core decrementer interrupt Li Tao-B22598
2009-09-09 11:16 ` Kenneth Johansson
2009-09-09 18:43 ` Scott Wood
2009-09-10 9:09 ` Kenneth Johansson [this message]
2009-09-10 11:53 ` Li Tao
2009-09-10 11:58 ` Li Tao
2009-09-10 15:30 ` Scott Wood
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=1252573794.10293.13.camel@localhost \
--to=kenneth@southpole.se \
--cc=B22598@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).