From: Kumar Gala <galak@kernel.crashing.org>
To: Liu Dave <DaveLiu@freescale.com>
Cc: Wood Scott <scottwood@freescale.com>,
"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>
Subject: Re: [PATCH 1/3] mpc83xx: Power Management support
Date: Thu, 26 Jun 2008 09:54:59 -0500 [thread overview]
Message-ID: <3BF4F03A-FD90-47BC-9F53-659848BE832E@kernel.crashing.org> (raw)
In-Reply-To: <58A20A281BAF1047B4EAE68DE5C0BDC201011622@zch01exm21.fsl.freescale.net>
On Jun 26, 2008, at 9:39 AM, Liu Dave wrote:
>>> Basic PM support for 83xx. Standby is implemented as sleep.
>>> Suspend-to-RAM is implemented as "deep sleep" (with the processor
>>> turned off) on 831x. PCI agent power management is supported.
>>>
>>> Device power management of SOC peripherals is not yet supported.
>>
>> (Not comments on this patch, but related)
>>
>> Do you know if anyone is looking at making sure DOZE/NAP work on
>> 83xx? We clearly don't flush the L1 cache today in the 6xx code.
>
> I did the test on 837x, the NAP did *not* work, due to the cache
> coherence issue.
> You are right, currently no flush L1 in the 6xx code, maybe it
> depend on
> the
> platform hardware capability.
Ben told me the pmac HW/chipsets did something here to ensure that the
core never actually went into NAP (or something like that) so they
didn't have to flush the caches.
- k
next prev parent reply other threads:[~2008-06-26 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 21:50 [PATCH 1/3] mpc83xx: Power Management support Scott Wood
2008-06-26 13:43 ` Kumar Gala
2008-06-26 14:07 ` Scott Wood
2008-06-26 14:39 ` Liu Dave
2008-06-26 14:54 ` Kumar Gala [this message]
2008-07-02 16:03 ` Kumar Gala
2008-07-02 16:38 ` Scott Wood
2008-07-02 17:06 ` Kumar Gala
2008-07-02 17:12 ` Scott Wood
2008-07-02 17:37 ` Kumar Gala
2008-07-02 17:46 ` 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=3BF4F03A-FD90-47BC-9F53-659848BE832E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=DaveLiu@freescale.com \
--cc=benh@au1.ibm.com \
--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).