From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/4] pm: Handle HID0_SLEEP in the TLF_NAPPING hack.
Date: Fri, 13 Jul 2007 13:04:28 -0500 [thread overview]
Message-ID: <4697BEAC.9090902@freescale.com> (raw)
In-Reply-To: <18071.7389.640461.229828@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Scott Wood writes:
>
>
>>The e300 core (and probably most other 6xx chips) can only come out of
>>sleep mode with an interrupt. However, interrupts are logically disabled
>>by the power management layer.
>
>
> On powerbooks it's typically a hard reset rather than an interrupt.
> Is it possible to use a hard reset on e300-based systems?
The 8313 can do this (see the deep sleep portion of the 83xx PM patch
that I posted), but others can't. Even on the 8313, it's not always
desireable to use deep sleep, due to limited wakeup sourcers, higher
latency, etc.
> Also, if you use an interrupt, presumably the cpu has to do something
> to clear the interrupt condition. What would that be?
The caller's MSR[EE] is cleared in power_save_6xx_restore, so the
interrupt won't happen again until the PM code re-enables MSR[EE].
-Scott
next prev parent reply other threads:[~2007-07-13 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 19:12 [PATCH 1/4] Make swsusp_32.S usable for suspend-to-RAM Scott Wood
2007-07-12 19:12 ` [PATCH 2/4] Implement arch disable/enable irq hooks Scott Wood
2007-07-13 10:10 ` Johannes Berg
2007-07-13 10:11 ` Johannes Berg
2007-07-12 19:13 ` [PATCH 3/4] pm: Handle HID0_SLEEP in the TLF_NAPPING hack Scott Wood
2007-07-13 6:34 ` Paul Mackerras
2007-07-13 18:04 ` Scott Wood [this message]
2007-07-12 19:13 ` [PATCH 4/4] Add 6xx-style HID0_SLEEP support Scott Wood
2007-09-05 19:12 ` Guennadi Liakhovetski
2007-09-05 19:14 ` 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=4697BEAC.9090902@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.