OMAP3: cpuidle: configure latencies/thresholds from board file
authorKevin Hilman <khilman@deeprootsystems.com>
Wed, 16 Dec 2009 00:37:18 +0000 (16:37 -0800)
committerKevin Hilman <khilman@deeprootsystems.com>
Tue, 23 Feb 2010 19:05:01 +0000 (11:05 -0800)
commitbb4de3df69e2993d642e38e17a3eccfe37845acc
tree3719204fb8430a28089ed12914e458fd84090be9
parent6af83b38613da58a221e56af676097575ce2c763
OMAP3: cpuidle: configure latencies/thresholds from board file

The CPUidle C state latencies and thresholds are dependent on various
board specific details.  This patch makes it possible to configure
these values from the respective board files.

omap3_pm_init_cpuidle() can now be optionally called from board files
to pass board specific cpuidle parameters.  If the board files do not
use this function to pass the params default values are used which
might cause higher consumption dur to wrong state selection by the
governor.

This patch only updates the 3430sdp board files to use
omap3_pm_init_cpuidle().

From Kalle, in addition to original patch from Rajendra:

Building without CONFIG_CPU_IDLE or CONFIG_PM causes build to fail if
cpu idle parameters are tried to pass using omap3_pm_init_cpuidle
function.

Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
arch/arm/mach-omap2/board-3430sdp.c
arch/arm/mach-omap2/cpuidle34xx.c
arch/arm/mach-omap2/pm.h