From: Scott Wood <scottwood@freescale.com>
To: Thomas Waldecker <Thomas.Waldecker@tqs.de>
Cc: "Linux PPC dev mailing list \(linuxppc-dev@lists.ozlabs.org\)"
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: Why is the e500v2 core not using cpuidle?
Date: Thu, 7 Feb 2013 12:01:56 -0600 [thread overview]
Message-ID: <1360260116.27002.3@snotra> (raw)
In-Reply-To: <B88C075EE1324644BA0452D5EFDD582813952706@TQ-MAIL.tq-net.de> (from Thomas.Waldecker@tqs.de on Thu Feb 7 06:19:25 2013)
On 02/07/2013 06:19:25 AM, Thomas Waldecker wrote:
> Hi Scott,
>=20
> I measured the power consumption of the whole system on the tqmp2020 =20
> ( http://tq-group.com/tqmp2020 )
> with a QorIQ P2020.
>=20
> Kernel:
> root@generic-powerpc-e500v2:/sys/power# uname -a
> Linux generic-powerpc-e500v2 3.7.0-rc8-00004-g6e93414 #4 SMP Tue Dec =20
> 11 08:53:23 CET 2012 ppc GNU/Linux
> root@generic-powerpc-e500v2:/sys/power# cat /etc/issue
> ELDK 5.2.1 \n \l
>=20
> In idle using doze I got:
> 545mA, 18V =3D> 9.81W
>=20
> In idle using nap I got:
> 500mA, 18V =3D> 9W
>=20
> That's a difference of 0.81W,
> 0.81W/9.81W =3D 0.083 (8.3 %)
Thanks.
> > The only way you'll get into sleep mode is through /sys/power/state.
>=20
> How can I use this interface?
>=20
> root@generic-powerpc-e500v2:/sys/power# ls -la
> total 0
> drwxr-xr-x 2 root root 0 Feb 1 15:39 .
> dr-xr-xr-x 12 root root 0 Feb 1 15:19 ..
> -rw-r--r-- 1 root root 4096 Feb 1 15:39 state
> root@generic-powerpc-e500v2:/sys/power# cat state
> root@generic-powerpc-e500v2:/sys/power# echo "sleep" > state
> -sh: echo: write error: Function not implemented
> root@generic-powerpc-e500v2:/sys/power# echo 0 > state
> -sh: echo: write error: Function not implemented
> root@generic-powerpc-e500v2:/sys/power#
Make sure that CONFIG_FSL_PMC is enabled, and that you have a pmc node =20
in the device tree. You'll only have standby, not sleep. mpc8536 and =20
p1022 can support what the chip calls "deep sleep" and is exposed as =20
"sleep" rather than "standby", but it doesn't look like the code for =20
that has made it into mainline Linux yet.
-Scott=
next prev parent reply other threads:[~2013-02-07 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 12:19 Why is the e500v2 core not using cpuidle? Thomas Waldecker
2013-02-07 18:01 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-02 9:41 AW: " Thomas Waldecker
2013-02-04 20:02 ` Scott Wood
2013-02-01 12:06 Thomas Waldecker
2013-02-01 18:15 ` 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=1360260116.27002.3@snotra \
--to=scottwood@freescale.com \
--cc=Thomas.Waldecker@tqs.de \
--cc=linuxppc-dev@lists.ozlabs.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.