From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: prodyut hazarika <prodyuth@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Support for low power mode for powerpc processors
Date: Fri, 04 Jul 2008 09:42:51 +1000 [thread overview]
Message-ID: <1215128571.7960.10.camel@pasglop> (raw)
In-Reply-To: <49c0ff980807031252w2c01406dk63bd7d932db37720@mail.gmail.com>
On Thu, 2008-07-03 at 12:52 -0700, prodyut hazarika wrote:
> But a lot of SoC like 440GT/EX support two modes of power save -
> - Cut off power to other cores like PCIExpress/USB/MAC/UART etc
> - Lower the CPU frequency
>
> Is it possible to scale down CPU freq or cut off power to unused cores
> while the CPU is idle? The ideal way would be that the SoC registers a
> set of handlers to the Kernel that can power off/up the SoC components
> or reduce/restore CPU frequency. Does any such framework exist for
> PowerPC processors, because most PowerPC based SoC (FreeScale/AMCC
> etc) support the above two modes of power save.
Cutting off power to individual cores should be done by the drivers for
those cores (let's call the devices). For example, the USB driver could
cut of power when nothing is connected, though I'm not sure if it can do
that without losing the ability to detect new connections, but then, USB
has a suspend state that should make it mostly unnecessary. For the
UART, you may lose the ability to receive.
At the end of the day, if you don't use at all a core, disable it from
your firmware and set it as unused in the device-tree.
Ben.
next prev parent reply other threads:[~2008-07-03 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 18:54 Support for low power mode for powerpc processors prodyut hazarika
2008-07-03 19:16 ` Josh Boyer
2008-07-03 19:52 ` prodyut hazarika
2008-07-03 23:42 ` Benjamin Herrenschmidt [this message]
2008-07-07 15:27 ` Josh Boyer
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=1215128571.7960.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=prodyuth@gmail.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).