From: Olof Johansson <olof@lixom.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Enable DEEPNAP power savings mode on 970MP
Date: Thu, 5 Oct 2006 09:21:15 -0500 [thread overview]
Message-ID: <20061005092115.6948663f@localhost.localdomain> (raw)
In-Reply-To: <1160026464.22232.16.camel@localhost.localdomain>
On Thu, 05 Oct 2006 15:34:24 +1000 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Isn't deep nap supposed to only get entered from F/4 which we never
> use ?
>
> Ben confused...
Nope.
The User Manual clearly talks about going in/out of deep nap from the
different powertune frequencies, see for example section 6.4.2 and 9.4.2.
-Olof
next prev parent reply other threads:[~2006-10-05 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 4:41 [PATCH] powerpc: Enable DEEPNAP power savings mode on 970MP Olof Johansson
2006-10-05 5:34 ` Benjamin Herrenschmidt
2006-10-05 14:21 ` Olof Johansson [this message]
2006-10-05 19:25 ` Michael Buesch
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=20061005092115.6948663f@localhost.localdomain \
--to=olof@lixom.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--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).