public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Norbert van Bolhuis <nvbolhuis@aimvalley•nl>
To: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Cannot wake-up from standby with MPC8313
Date: Wed, 04 Jan 2012 17:19:04 +0100	[thread overview]
Message-ID: <4F047BF8.7090400@aimvalley.nl> (raw)


after entering:

echo standby > /sys/power/state

I'm unable to wake up the MPC8313 (on our custom designed
MPC8313 board).

I need it to wake up through GPIO IRQ.
I cause multiple GPIO interrupts (all properly handled by an isr),
but the MPC8313 does not wake up.

How should one wake up via GPGIO IRQ ?

I'm using v2.6.29 and I wonder whether this is related to
our custom 8313 board and/or v2.6.29 and/or missing kernel
patches or maybe this never worked ?

Also, I do not understand line 220 of arch/powerpc/platforms/83xx/suspend.c

219         } else {
220                 out_be32(&pmc_regs->mask, PMCER_PMCI);
221
222                 mpc6xx_enter_standby();

How can wake up ever work if TSEC/GPIO/TIMER/etc.. wake up events
are disabled ?

changing this into "out_be32(&pmc_regs->mask, PMCER_PMCI|PMCER_GPIO);"
gives same result.

MPC8313 is in PCI HOST mode and here's a relevant part
of the DTS:

         pmc: power@b00 {
             compatible = "fsl,mpc8313-pmc", "fsl,mpc8349-pmc";
             reg = <0xb00 0x100 0xa00 0x100>;
             interrupts = <80 8>;
             interrupt-parent = <&ipic>;
             fsl,mpc8313-wakeup-timer = <&gtm1>;

             /* Remove this (or change to "okay") if you have
              * a REVA3 or later board, if you apply one of the
              * workarounds listed in section 8.5 of the board
              * manual, o if you are adapting this device treeSE=
              * to a different board.
              */
             status = "okay";
         };

         gtm1: timer@500 {
             compatible = "fsl,mpc8313-gtm", "fsl,gtm";
             reg = <0x500 0x100>;
             interrupts = <90 8 78 8 84 8 72 8>;
             interrupt-parent = <&ipic>;
         };


Any help/advice/answer is more than welcome.

---
NvBolhuis

             reply	other threads:[~2012-01-04 17:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 16:19 Norbert van Bolhuis [this message]
2012-01-04 21:08 ` Cannot wake-up from standby with MPC8313 Scott Wood
2012-01-05 15:58   ` Norbert van Bolhuis
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=4F047BF8.7090400@aimvalley.nl \
    --to=nvbolhuis@aimvalley$(echo .)nl \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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