OMAP3: clean-up mach specific cpuidle data structures
- 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> Signed-off-by: Kevin Hilman <khilman@ti.com>
This commit is contained in:
@@ -36,11 +36,16 @@ static inline int omap4_opp_init(void)
|
||||
}
|
||||
#endif
|
||||
|
||||
/*
|
||||
* cpuidle mach specific parameters
|
||||
*
|
||||
* The board code can override the default C-states definition using
|
||||
* omap3_pm_init_cpuidle
|
||||
*/
|
||||
struct cpuidle_params {
|
||||
u8 valid;
|
||||
u32 sleep_latency;
|
||||
u32 wake_latency;
|
||||
u32 threshold;
|
||||
u32 exit_latency; /* exit_latency = sleep + wake-up latencies */
|
||||
u32 target_residency;
|
||||
u8 valid; /* validates the C-state */
|
||||
};
|
||||
|
||||
#if defined(CONFIG_PM) && defined(CONFIG_CPU_IDLE)
|
||||
|
Reference in New Issue
Block a user