From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 2/5] OMAP3: clean-up mach specific cpuidle data structures
Date: Wed, 04 May 2011 13:09:08 -0700 [thread overview]
Message-ID: <8762pqrzx7.fsf@ti.com> (raw)
In-Reply-To: <1304069186-3086-3-git-send-email-j-pihet@ti.com> (jean pihet's message of "Fri, 29 Apr 2011 11:26:23 +0200")
jean.pihet@newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti.com>
>
> - sleep_latency and wake_latency are not used, replace them by
> exit_latency which is used by cpuidle. exit_latency simply is
> the sum of sleep_latency and wake_latency,
> - replace threshold by target_residency,
> - changed the OMAP3 specific cpuidle code accordingly,
> - changed the OMAP3 board code accordingly.
>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>
One minor comment...
> ---
> arch/arm/mach-omap2/board-rx51.c | 15 +++---
> arch/arm/mach-omap2/cpuidle34xx.c | 103 +++++++++++++++---------------------
> arch/arm/mach-omap2/pm.h | 13 +++--
> 3 files changed, 60 insertions(+), 71 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-rx51.c b/arch/arm/mach-omap2/board-rx51.c
> index f8ba20a..44656e8 100644
> --- a/arch/arm/mach-omap2/board-rx51.c
> +++ b/arch/arm/mach-omap2/board-rx51.c
> @@ -58,21 +58,22 @@ static struct platform_device leds_gpio = {
> },
> };
>
> +/* cpuidle C-states definition override from the default values */
Please add a line here describing the sum in the table entries
(e.g. it's sleep + wakeup latency.)
> static struct cpuidle_params rx51_cpuidle_params[] = {
> /* C1 */
> - {1, 110, 162, 5},
> + {110 + 162, 5 , 1},
> /* C2 */
> - {1, 106, 180, 309},
> + {106 + 180, 309, 1},
> /* C3 */
> - {0, 107, 410, 46057},
> + {107 + 410, 46057, 0},
> /* C4 */
> - {0, 121, 3374, 46057},
> + {121 + 3374, 46057, 0},
> /* C5 */
> - {1, 855, 1146, 46057},
> + {855 + 1146, 46057, 1},
> /* C6 */
> - {0, 7580, 4134, 484329},
> + {7580 + 4134, 484329, 0},
> /* C7 */
> - {1, 7505, 15274, 484329},
> + {7505 + 15274, 484329, 1},
> };
Kevin
next prev parent reply other threads:[~2011-05-04 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 9:26 [PATCH 0/5] OMAP: cpuidle code clean-up jean.pihet
2011-04-29 9:26 ` [PATCH 1/5] OMAP3 cpuidle: remove useless SDP specific timings jean.pihet
2011-04-29 11:14 ` Santosh Shilimkar
2011-05-04 14:40 ` Kevin Hilman
2011-04-29 9:26 ` [PATCH 2/5] OMAP3: clean-up mach specific cpuidle data structures jean.pihet
2011-05-04 20:09 ` Kevin Hilman [this message]
2011-04-29 9:26 ` [PATCH 3/5] OMAP3: cpuidle: re-organize the C-states data jean.pihet
2011-04-29 11:24 ` Santosh Shilimkar
2011-05-04 14:59 ` Kevin Hilman
2011-04-29 9:26 ` [PATCH 4/5] OMAP3: cpuidle: code rework for improved readability jean.pihet
2011-05-04 15:32 ` Kevin Hilman
2011-04-29 9:26 ` [PATCH 5/5] OMAP3: cpuidle: change the power domains modes determination logic jean.pihet
2011-04-29 11:29 ` Santosh Shilimkar
2011-04-29 14:00 ` 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=8762pqrzx7.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox