linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: Scott Wood <scottwood@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Cannot wake-up from standby with MPC8313
Date: Thu, 05 Jan 2012 16:58:58 +0100	[thread overview]
Message-ID: <4F05C8C2.9070401@aimvalley.nl> (raw)
In-Reply-To: <4F04BFEA.1050009@freescale.com>

On 01/04/12 22:08, Scott Wood wrote:

...

> It's been a while since I've touched this, but IIRC the PMC events are
> mainly important for deep sleep, and for normal sleep (standby) you can
> wake from any interrupt other than core interrupts like timebase.  I'm
> not sure to what extent setting PMCCR[SLPEN] affects this -- I don't see
> where the documentation says what "system low power state" means.  I
> would be surprised if GPIO were affected, though, since it's supported
> as a wakeup source even in deep sleep.  I think I was able to wake from
> standby on a UART interrupt even with SLPEN set.
>
> Are you sure the GPIO block is asserting an interrupt, and that it
> hasn't been masked during the preparation for standby?
>
> What happens if you modify mpc6xx_enter_standby() to not actually set
> MSR_POW?
>


thanks for your response.

not setting MSR_POW gives same result.

if I set kernel.powersave-nap=1 it works fine, so apparently
NAP/DOZE mode does work (if CPU is idle). This saves almost no
power though. Standby mode saves about 300-500 mW.

The problem could well be our board though, today I learned it does
work by connecting an (inactive) JTAG debugger.
Also, on another board it always works.

And indeed wake-up occurs through GPIO interrupt or UART interrupt
(key press on console).


---
NvBolhuis

  reply	other threads:[~2012-01-05 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 16:19 Cannot wake-up from standby with MPC8313 Norbert van Bolhuis
2012-01-04 21:08 ` Scott Wood
2012-01-05 15:58   ` Norbert van Bolhuis [this message]
2012-01-05 18:22     ` Scott Wood
2012-01-06 13:53       ` Norbert van Bolhuis
2012-01-06 21:03         ` Scott Wood
2012-01-13 14:13           ` Norbert van Bolhuis
2012-01-16 20:22             ` Scott Wood
2012-01-17 16:56               ` Norbert van Bolhuis
2012-01-17 22:09                 ` Scott Wood
2012-01-18 10:16                   ` Norbert van Bolhuis
2012-01-20 20:05                     ` Scott Wood
2012-01-23 10:08                       ` ehodys
  -- strict thread matches above, loose matches on Subject: below --
2012-01-23  9:34 nvbolhuis

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=4F05C8C2.9070401@aimvalley.nl \
    --to=nvbolhuis@aimvalley.nl \
    --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).