ARM: OMAP: Fix OMAP1 compilation after MPUIO check change.

ARM: OMAP: Fix OMAP1 compilation after MPUIO check change.

[Jonathan McDowell]

The recent MPUIO range change fix breaks compilation if
CONFIG_ARCH_OMAP24XX isn't defined; it should be OMAP_MAX_GPIO_LINES not
MAX_GPIO_LINES I believe. This one liner fixes it.

Signed-Off-By: Jonathan McDowell <noodles@earth.li>

-----
diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
index d5221b2..b27ba0e 100644
--- a/arch/arm/plat-omap/gpio.c
+++ b/arch/arm/plat-omap/gpio.c
@@ -216,7 +216,7 @@ static inline int gpio_valid(int gpio)
 		return -1;
 #ifndef CONFIG_ARCH_OMAP24XX
 	if (OMAP_GPIO_IS_MPUIO(gpio)) {
-		if (gpio >= MAX_GPIO_LINES + 16)
+		if (gpio >= OMAP_MAX_GPIO_LINES + 16)
 			return -1;
 		return 0;
 	}
-----

J.

-- 
noodles is not a sign of poor table manners

Re: ARM: OMAP: Fix OMAP1 compilation after MPUIO check change.

[Mark Howell]

Jonathan McDowell wrote:
> The recent MPUIO range change fix breaks compilation if
> CONFIG_ARCH_OMAP24XX isn't defined; it should be OMAP_MAX_GPIO_LINES not
> MAX_GPIO_LINES I believe. This one liner fixes it.
> 

Thanks, this works for me on my 1611 H2 with today's 2.6.18-rc4 from
git. Mark.

Re: ARM: OMAP: Fix OMAP1 compilation after MPUIO check change.

[Tony Lindgren]

* Mark Howell <mhowell@northlink.com> [060810 02:47]:
> Jonathan McDowell wrote:
> >The recent MPUIO range change fix breaks compilation if
> >CONFIG_ARCH_OMAP24XX isn't defined; it should be OMAP_MAX_GPIO_LINES not
> >MAX_GPIO_LINES I believe. This one liner fixes it.
> >
> 
> Thanks, this works for me on my 1611 H2 with today's 2.6.18-rc4 from
> git. Mark.

Good to hear! Pushing today.

Tony