From: Rajendra Nayak <rnayak@ti.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com,
linux-arm-kernel@lists.infradead.org, khilman@ti.com,
Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 07/10] ARM: OMAP3: update cpuidle latency and threshold figures
Date: Wed, 20 Jun 2012 16:31:31 +0530 [thread overview]
Message-ID: <4FE1AD8B.305@ti.com> (raw)
In-Reply-To: <1339686361-11526-8-git-send-email-j-pihet@ti.com>
On Thursday 14 June 2012 08:35 PM, Jean Pihet wrote:
> {
> .enter = omap3_enter_idle_bm,
> - .exit_latency = 3000 + 8500,
> - .target_residency = 15000,
> + .exit_latency = 4080 + 801,
> + .target_residency = 215000,
> .flags = CPUIDLE_FLAG_TIME_VALID,
> .name = "C6",
> .desc = "MPU OFF + CORE RET",
> },
> {
> .enter = omap3_enter_idle_bm,
> - .exit_latency = 10000 + 30000,
> - .target_residency = 30000,
> + .exit_latency = 4300 + 13000,
> + .target_residency = 215000,
Is the target_residency same for both these states?
> .flags = CPUIDLE_FLAG_TIME_VALID,
> .name = "C7",
> .desc = "MPU OFF + CORE OFF",
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/10] ARM: OMAP3: update cpuidle latency and threshold figures
Date: Wed, 20 Jun 2012 16:31:31 +0530 [thread overview]
Message-ID: <4FE1AD8B.305@ti.com> (raw)
In-Reply-To: <1339686361-11526-8-git-send-email-j-pihet@ti.com>
On Thursday 14 June 2012 08:35 PM, Jean Pihet wrote:
> {
> .enter = omap3_enter_idle_bm,
> - .exit_latency = 3000 + 8500,
> - .target_residency = 15000,
> + .exit_latency = 4080 + 801,
> + .target_residency = 215000,
> .flags = CPUIDLE_FLAG_TIME_VALID,
> .name = "C6",
> .desc = "MPU OFF + CORE RET",
> },
> {
> .enter = omap3_enter_idle_bm,
> - .exit_latency = 10000 + 30000,
> - .target_residency = 30000,
> + .exit_latency = 4300 + 13000,
> + .target_residency = 215000,
Is the target_residency same for both these states?
> .flags = CPUIDLE_FLAG_TIME_VALID,
> .name = "C7",
> .desc = "MPU OFF + CORE OFF",
next prev parent reply other threads:[~2012-06-20 11:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 15:05 [PATCH v8 00/10] PM QoS: implement the OMAP low level constraints management code Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 01/10] ARM: OMAP2+: PM QoS: control the power domains next state from the constraints Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-15 11:37 ` Jean Pihet
2012-06-15 11:37 ` Jean Pihet
2012-07-19 9:12 ` Menon, Nishanth
2012-07-19 9:12 ` Menon, Nishanth
2012-07-20 3:08 ` Menon, Nishanth
2012-07-20 3:08 ` Menon, Nishanth
2012-06-14 15:05 ` [PATCH 02/10] ARM: OMAP2+: hwmod: manage the wake-up latency constraints Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 03/10] ARM: OMAP2+: PM QoS: manage the per-device latency constraints in hwmod Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-20 10:29 ` Rajendra Nayak
2012-06-20 10:29 ` Rajendra Nayak
2012-06-20 11:38 ` Jean Pihet
2012-06-20 11:38 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 04/10] ARM: OMAP: omap_device: register to the per-device PM QoS framework Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-20 10:41 ` Rajendra Nayak
2012-06-20 10:41 ` Rajendra Nayak
2012-07-19 9:21 ` Menon, Nishanth
2012-07-19 9:21 ` Menon, Nishanth
2012-06-14 15:05 ` [PATCH 05/10] ARM: OMAP3: cpuidle: next C-state decision depends on the PM QoS MPU and CORE constraints Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 06/10] ARM: OMAP3: PM: cpuidle: default to C1 in next_valid_state Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 07/10] ARM: OMAP3: update cpuidle latency and threshold figures Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-20 11:01 ` Rajendra Nayak [this message]
2012-06-20 11:01 ` Rajendra Nayak
2012-06-20 11:39 ` Jean Pihet
2012-06-20 11:39 ` Jean Pihet
2012-06-14 15:05 ` [PATCH 08/10] ARM: OMAP3: powerdomain data: add wake-up latency figures Jean Pihet
2012-06-14 15:05 ` Jean Pihet
2012-06-14 15:06 ` [PATCH 09/10] ARM: OMAP: convert I2C driver to PM QoS for latency constraints Jean Pihet
2012-06-14 15:06 ` Jean Pihet
2012-06-14 15:06 ` [PATCH 10/10] ARM: OMAP: PM: remove the latency related functions from the API Jean Pihet
2012-06-14 15:06 ` 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=4FE1AD8B.305@ti.com \
--to=rnayak@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.