From: jean.pihet@newoldbits.com
To: Kevin Hilman <khilman@ti.com>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-omap@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Walmsley <paul@pwsan.co>
Cc: Jean Pihet <j-pihet@ti.com>
Subject: [PATCH 7/8] OMAP3: update cpuidle latency and threshold figures
Date: Wed, 21 Sep 2011 18:24:17 +0200 [thread overview]
Message-ID: <1316622258-3892-8-git-send-email-j-pihet@ti.com> (raw)
In-Reply-To: <1316622258-3892-1-git-send-email-j-pihet@ti.com>
From: Jean Pihet <j-pihet@ti.com>
Update the data from the measurements performed at HW and SW levels.
Cf. http://www.omappedia.org/wiki/Power_Management_Device_Latencies_Measurement
for a detailed explanation on where are the numbers magically coming from.
ToDo:
- Measure the wake-up latencies for all power domains for OMAP3
- Correct some numbers when sys_clkreq and sys_offmode are supported
Signed-off-by: Jean Pihet <j-pihet@ti.com>
---
arch/arm/mach-omap2/cpuidle34xx.c | 28 ++++++++++++++--------------
1 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/arch/arm/mach-omap2/cpuidle34xx.c b/arch/arm/mach-omap2/cpuidle34xx.c
index 1b8e0da..4b3e994 100644
--- a/arch/arm/mach-omap2/cpuidle34xx.c
+++ b/arch/arm/mach-omap2/cpuidle34xx.c
@@ -44,20 +44,20 @@
* pass these details from the board file.
*/
static struct cpuidle_params cpuidle_params_table[] = {
- /* C1 */
- {2 + 2, 5, 1},
- /* C2 */
- {10 + 10, 30, 1},
- /* C3 */
- {50 + 50, 300, 1},
- /* C4 */
- {1500 + 1800, 4000, 1},
- /* C5 */
- {2500 + 7500, 12000, 1},
- /* C6 */
- {3000 + 8500, 15000, 1},
- /* C7 */
- {10000 + 30000, 300000, 1},
+ /* C1 . MPU WFI + Core active */
+ {73 + 78, 152, 1},
+ /* C2 . MPU WFI + Core inactive */
+ {165 + 88, 345, 1},
+ /* C3 . MPU CSWR + Core inactive */
+ {163 + 182, 345, 1},
+ /* C4 . MPU OFF + Core inactive */
+ {2852 + 605, 150000, 1},
+ /* C5 . MPU RET + Core RET */
+ {800 + 366, 2120, 1},
+ /* C6 . MPU OFF + Core RET */
+ {4080 + 801, 215000, 1},
+ /* C7 . MPU OFF + Core OFF */
+ {4300 + 13000, 215000, 1},
};
#define OMAP3_NUM_STATES ARRAY_SIZE(cpuidle_params_table)
--
1.7.4.1
next prev parent reply other threads:[~2011-09-21 16:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 16:14 [PATCH v2 0/8] PM QoS: implement the OMAP low level constraints management code Jean Pihet
2011-09-21 16:14 ` [PATCH 1/8] OMAP: convert I2C driver to PM QoS for latency constraints Jean Pihet
2011-09-21 16:14 ` [PATCH 2/8] OMAP: PM: remove the latency related functions from the API Jean Pihet
2011-09-21 16:14 ` [PATCH 3/8] OMAP2+: powerdomain: control power domains next state Jean Pihet
2011-09-21 16:14 ` [PATCH 4/8] OMAP2+: omap_hwmod: manage the wake-up latency constraints Jean Pihet
2011-09-21 16:14 ` [PATCH 5/8] OMAP: PM: register to the per-device PM QoS framework Jean Pihet
2011-09-21 16:14 ` [PATCH 6/8] OMAP3: cpuidle: next C-state decision depends on the PM QoS MPU and CORE constraints Jean Pihet
2011-09-21 16:14 ` [PATCH 7/8] OMAP3: update cpuidle latency and threshold figures Jean Pihet
2011-10-12 2:48 ` Ming Lei
2011-10-12 7:29 ` Jean Pihet
2011-09-21 16:14 ` [PATCH 8/8] OMAP3: powerdomain data: add wake-up latency figures Jean Pihet
2011-09-21 16:24 ` [PATCH v2 0/8] PM QoS: implement the OMAP low level constraints management code jean.pihet
2011-09-21 16:24 ` [PATCH 1/8] OMAP: convert I2C driver to PM QoS for latency constraints jean.pihet
2011-09-21 16:24 ` [PATCH 2/8] OMAP: PM: remove the latency related functions from the API jean.pihet
2011-09-21 16:24 ` [PATCH 3/8] OMAP2+: powerdomain: control power domains next state jean.pihet
2011-09-21 16:24 ` [PATCH 4/8] OMAP2+: omap_hwmod: manage the wake-up latency constraints jean.pihet
2011-10-07 2:53 ` Paul Walmsley
2011-10-10 8:08 ` Jean Pihet
2011-10-12 15:27 ` Jean Pihet
2011-09-21 16:24 ` [PATCH 5/8] OMAP: PM: register to the per-device PM QoS framework jean.pihet
2011-09-21 16:24 ` [PATCH 6/8] OMAP3: cpuidle: next C-state decision depends on the PM QoS MPU and CORE constraints jean.pihet
2011-09-21 16:24 ` jean.pihet [this message]
2011-09-21 16:24 ` [PATCH 8/8] OMAP3: powerdomain data: add wake-up latency figures jean.pihet
2011-10-07 4:17 ` Paul Walmsley
2011-10-10 8:17 ` Jean Pihet
2011-10-10 22:44 ` Paul Walmsley
2011-10-10 22:52 ` Paul Walmsley
2011-10-11 6:50 ` Pihet-XID, Jean
2011-10-07 15:26 ` Paul Walmsley
2011-10-10 8:19 ` Jean Pihet
2011-09-21 16:27 ` [PATCH v2 0/8] PM QoS: implement the OMAP low level constraints management code Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2011-10-12 15:24 [PATCH v3 " jean.pihet
2011-10-12 15:24 ` [PATCH 7/8] OMAP3: update cpuidle latency and threshold figures jean.pihet
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=1316622258-3892-8-git-send-email-j-pihet@ti.com \
--to=jean.pihet@newoldbits.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=paul@pwsan.co \
--cc=rjw@sisk.pl \
/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