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: Fri, 13 Jan 2012 15:13:43 +0100 [thread overview]
Message-ID: <4F103C17.3080003@aimvalley.nl> (raw)
In-Reply-To: <4F076187.2080308@freescale.com>
On 01/06/12 22:03, Scott Wood wrote:
> On 01/06/2012 07:53 AM, Norbert van Bolhuis wrote:
>> On 01/05/12 19:22, Scott Wood wrote:
>>> On 01/05/2012 09:58 AM, Norbert van Bolhuis wrote:
>>>> thanks for your response.
>>>>
>>>> not setting MSR_POW gives same result.
>>>
>>> OK, so you're not getting an interrupt regardless of low-power state.
>>>
>>> Check whether the interrupt is getting masked during standby preparation.
>>>
>>> Does the interrupt handler run when you're not trying to enter standby?
>>>
>>
>>
>> The GPIO/UART interrupt nor the PMC interrupt are being masked during
>> standby
>> preperation.
>> The GPIO/UART interrupt works fine in "operational" mode.
>> The PMC interrupt I do not know, is it possible to to get PMC interrupt
>> without going to standby or deep-sleep ?
>
> The PMC interrupt is mainly of interest when running as a PCI agent, to
> be notified when the host changed the desired suspend state in config space.
>
> What changes from operational mode to the test where you omit setting
> MSR_POW?
>
> Try dumping SIPNR/SIMSR and GPIER/GPIMR/GPDAT at various points.
>
I dumped SIPNR/SIMSR and uart IIR/EIR (since console triggers wake-up)
but they do not change just before entering standby (via mpc6xx_enter_standby
which omits setting MSR_POW). uart IRQ is always enabled, unmasked and
not pending.
I tried to log to physical memory to see what's going on whenever the
board fails to wake-up.
(I can examine physical memory after CPU is stuck in sleep, by connecting
a JTAG debugger, start u-boot and stop after DDR2 SDRAM ctrl is
re-configured)
It looks like an interupt does occur, but do_IRQ seems to be stuck
in ppc_md.get_irq=ipic_get_irq where it reads SIVCR.
I have no idea why, any more suggestions ?
---
NvBolhuis
next prev parent reply other threads:[~2012-01-13 14:13 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
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 [this message]
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=4F103C17.3080003@aimvalley.nl \
--to=nvbolhuis@aimvalley$(echo .)nl \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/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