> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Gupta, Ajay Kumar > Sent: Wednesday, October 28, 2009 5:13 PM [...] > > Signed-off-by: Ajay Kumar Gupta <ajay.gupta@xxxxxx> > --- > arch/arm/mach-omap2/mux.c | 7 +++++++ > arch/arm/plat-omap/include/plat/mux.h | 5 +++++ > 2 files changed, 12 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c > index 32c953e..00ad592 100644 > --- a/arch/arm/mach-omap2/mux.c > +++ b/arch/arm/mach-omap2/mux.c > @@ -551,6 +551,13 @@ MUX_CFG_34XX("AF13_3430_MMC3_DAT3", 0x5e2, > MUX_CFG_34XX("AF26_34XX_SYS_NIRQ", 0x1E0, > OMAP3_WAKEUP_EN | OMAP34XX_PIN_INPUT_PULLUP | > OMAP34XX_MUX_MODE0) > +/* EHCI GPIO's on OMAP3EVM (Rev >= E) */ > +MUX_CFG_34XX("AH14_34XX_GPIO21", 0x5ea, > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP) > +MUX_CFG_34XX("AF9_34XX_GPIO22", 0x5ec, > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP) > +MUX_CFG_34XX("U3_34XX_GPIO61", 0x0c8, > + OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP) Apologies, but cant the bootloader handle this? do we want to wait for cleanup of mux system before doing this? Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
