Jon Hunter <[email protected]> writes: > From: Jon Hunter <[email protected]> > > The OMAP2+ timer code has a definition for the maximum number of timers that > OMAP2+ devices have. This defintion is not used anywhere in the code and > appears to be left over. Furthermore the definition is not accurate for OMAP4 > devices that only have 11 timers available because the 12th timer is reserved > as a secure timer. Therefore, remove this definition.
changelog nit: the 12th timer is secure on OMAP3 HS devices also. Kevin > Signed-off-by: Jon Hunter <[email protected]> > --- > arch/arm/mach-omap2/timer.c | 3 --- > 1 files changed, 0 insertions(+), 3 deletions(-) > > diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c > index 840929b..c030dfe 100644 > --- a/arch/arm/mach-omap2/timer.c > +++ b/arch/arm/mach-omap2/timer.c > @@ -69,9 +69,6 @@ > #define OMAP3_SECURE_TIMER 1 > #endif > > -/* MAX_GPTIMER_ID: number of GPTIMERs on the chip */ > -#define MAX_GPTIMER_ID 12 > - > static u32 sys_timer_reserved; > > /* Clockevent code */ -- 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
