From: Jarkko Nikula <jhnikula@gmail.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, khilman@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap3: cpuidle: Add description field to each C-state.
Date: Fri, 11 Feb 2011 19:07:23 +0200 [thread overview]
Message-ID: <20110211190723.b93bcb60.jhnikula@gmail.com> (raw)
In-Reply-To: <1297437132-1005-2-git-send-email-santosh.shilimkar@ti.com>
On Fri, 11 Feb 2011 20:42:12 +0530
Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
> Add a description field to each idle C-state. This helps to give
> better data with PowerTop and one don't have to refer to the code
> to link what Cx means from system point of view while analysing
> PowerTop data.
>
> No functional change.
>
Out of curiosity what powertop version is required to get these handy
descriptions visible?
As I see these in /sys/devices/system/cpu/cpu0/cpuidle/stateX/desc it's
fair to give my tested by
Tested-by: Jarkko Nikula <jhnikula@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: jhnikula@gmail.com (Jarkko Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3: cpuidle: Add description field to each C-state.
Date: Fri, 11 Feb 2011 19:07:23 +0200 [thread overview]
Message-ID: <20110211190723.b93bcb60.jhnikula@gmail.com> (raw)
In-Reply-To: <1297437132-1005-2-git-send-email-santosh.shilimkar@ti.com>
On Fri, 11 Feb 2011 20:42:12 +0530
Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
> Add a description field to each idle C-state. This helps to give
> better data with PowerTop and one don't have to refer to the code
> to link what Cx means from system point of view while analysing
> PowerTop data.
>
> No functional change.
>
Out of curiosity what powertop version is required to get these handy
descriptions visible?
As I see these in /sys/devices/system/cpu/cpu0/cpuidle/stateX/desc it's
fair to give my tested by
Tested-by: Jarkko Nikula <jhnikula@gmail.com>
next prev parent reply other threads:[~2011-02-11 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 15:12 [PATCH] omap3: pm: Use exported set_cr() instead of a custom one Santosh Shilimkar
2011-02-11 15:12 ` Santosh Shilimkar
2011-02-11 15:12 ` [PATCH] omap3: cpuidle: Add description field to each C-state Santosh Shilimkar
2011-02-11 15:12 ` Santosh Shilimkar
2011-02-11 17:07 ` Jarkko Nikula [this message]
2011-02-11 17:07 ` Jarkko Nikula
2011-02-12 7:42 ` Santosh Shilimkar
2011-02-12 7:42 ` Santosh Shilimkar
2011-03-04 1:41 ` Kevin Hilman
2011-03-04 1:41 ` Kevin Hilman
2011-02-15 0:08 ` [PATCH] omap3: pm: Use exported set_cr() instead of a custom one Kevin Hilman
2011-02-15 0:08 ` 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=20110211190723.b93bcb60.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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 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.