All of lore.kernel.org
 help / color / mirror / Atom feed
From: javier Martin <javier.martin@vista-silicon.com>
To: linux-omap@vger.kernel.org
Cc: Koen Kooi <koen@beagleboard.org>
Subject: cpuidle status in mainline for Beagleboard xM
Date: Thu, 1 Sep 2011 16:14:00 +0200	[thread overview]
Message-ID: <CACKLOr10aTCwkBZnSinvP4HLPhrJeiBs=6KM2we4DwTT0NJ22A@mail.gmail.com> (raw)

Hi,
I am trying to enable cpuidle and cpufreq support in latest stable
kernel (3.0.4) in the Beagleboard xM.
The default governor I've selected in the kernel menu is "powersave".
However, when I execute powertop 1.12 (downloaded from Angstrom 2010.x
repository through opkg) I get the following:


Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 0.4%)
C0               16.7ms (99.6%)
C1                0.0ms ( 0.0%)
C2                0.0ms ( 0.0%)
C3                0.0ms ( 0.0%)
C4                0.0ms ( 0.0%)
C5                0.0ms ( 0.0%)
C6                0.0ms ( 0.0%)

So, the CPU always stays in C0 status and P-states are not shown. I've
read some old reports of this working properly in omap-pm-next branch
http://groups.google.com/group/beagleboard/browse_thread/thread/b03e08868af7c6e0?pli=1%29
Do cpuidle and cpufreq really work in mainline?

Thank you.

--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-09-01 14:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 14:14 javier Martin [this message]
2011-09-01 15:10 ` cpuidle status in mainline for Beagleboard xM Kevin Hilman
2011-09-01 15:33   ` javier Martin
2011-09-01 17:46     ` Kevin Hilman
2011-09-02  6:05       ` Jarkko Nikula
2011-09-02  7:23         ` javier Martin
2011-09-02 17:14           ` Kevin Hilman
2011-09-05  8:04             ` javier Martin
2011-09-06 21:04               ` Kevin Hilman

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='CACKLOr10aTCwkBZnSinvP4HLPhrJeiBs=6KM2we4DwTT0NJ22A@mail.gmail.com' \
    --to=javier.martin@vista-silicon.com \
    --cc=koen@beagleboard.org \
    --cc=linux-omap@vger.kernel.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.