Paul Walmsley <[email protected]> writes: > For MPU latency constraints to work, CONFIG_CPU_IDLE must be enabled, > since CPUIdle is where the constraints are evaluated. Warn during > compilation if CONFIG_CPU_IDLE is not defined. > > Signed-off-by: Paul Walmsley <[email protected]>
Thanks, pushing to PM branch. Kevin > --- > arch/arm/mach-omap2/resource34xx.c | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-omap2/resource34xx.c > b/arch/arm/mach-omap2/resource34xx.c > index 25535a3..1693e9b 100644 > --- a/arch/arm/mach-omap2/resource34xx.c > +++ b/arch/arm/mach-omap2/resource34xx.c > @@ -28,6 +28,10 @@ > #include "cm.h" > #include "cm-regbits-34xx.h" > > +#ifndef CONFIG_CPU_IDLE > +#warning MPU latency constraints require CONFIG_CPU_IDLE to function! > +#endif > + > /** > * init_latency - Initializes the mpu/core latency resource. > * @resp: Latency resource to be initalized > -- > 1.6.3.GIT -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
