From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] pm: Handle HID0_SLEEP in the TLF_NAPPING hack.
Date: Tue, 11 Sep 2007 16:50:45 -0500 [thread overview]
Message-ID: <46E70DB5.4050500@freescale.com> (raw)
In-Reply-To: <18151.2374.68378.969061@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.
>>
>> This hack extends the existing doze/nap hack to also suppress the running
>> of the interrupt handler when in sleep mode.
>
> Having thought about this for a bit, I have come to the conclusion
> that it would be a lot cleaner to use a new TLF_SLEEPING bit rather
> than having to read HID0 to know whether we were napping or sleeping.
> There are plenty of bits left in thread_info.local_flags; we've only
> used 1 so far. :)
OK.
-Scott
next prev parent reply other threads:[~2007-09-11 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 22:04 [PATCH v2] Check _PAGE_RW and _PAGE_PRESENT on kernel addresses Scott Wood
2007-09-05 22:06 ` [PATCH 2/3] pm: Handle HID0_SLEEP in the TLF_NAPPING hack Scott Wood
2007-09-11 21:31 ` Paul Mackerras
2007-09-11 21:50 ` Scott Wood [this message]
2007-09-05 22:06 ` [PATCH 3/3] Add 6xx-style HID0_SLEEP support Scott Wood
2007-09-11 21:34 ` Paul Mackerras
2007-09-11 21:47 ` Scott Wood
2007-09-05 22:08 ` [PATCH 4/3] Make swsusp_32.S usable for suspend-to-RAM Scott Wood
2007-11-07 12:25 ` Johannes Berg
2007-11-08 15:56 ` 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=46E70DB5.4050500@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 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).