"Hemanth V" <hemanthv@xxxxxx> writes:
> ----- Original Message -----
> From: "Gadiyar, Anand" <gadiyar@xxxxxx>
> To: "V, Hemanth" <hemanthv@xxxxxx>; "Kevin Hilman"
> <khilman@xxxxxxxxxxxxxxxxxxx>
>
>
>> >> Index: linux-omap-2.6/arch/arm/mach-omap2/devices.c
>> >> ===================================================================
>> >> --- linux-omap-2.6.orig/arch/arm/mach-omap2/devices.c 2009-05-14
>> >> 12:38:50.000000000 +0530
>> >> +++ linux-omap-2.6/arch/arm/mach-omap2/devices.c 2009-05-15 >>
>> 16:53:38.000000000 +0530
>
> <snip>
>
>> >> };
>> >>
>> >> static struct resource omap2_mcspi2_resources[] = {
>> >> @@ -351,6 +359,14 @@
>> >>
>> >> static void omap_init_mcspi(void)
>> >> {
>> >> +
>> >> + if (cpu_is_omap3430()) {
>> >> + omap_cfg_reg(AA3_3430_McSPI2_CLK);
>> >> + omap_cfg_reg(Y2_3430_McSPI2_SIMO);
>> >> + omap_cfg_reg(Y3_3430_McSPI2_SOMI);
>> >> + omap_cfg_reg(Y4_3430_McSPI2_CS0);
>> >> + }
>> >> +
>
>>This will change the mux mode for these pads for all OMAP3 boards,
>>even if they do not wish to use McSPI2. In particular, Beagleboard
>>will be affected as it uses HSUSB on Port2 and these pads overlap.
>
> I could add an option like below to plat-omap/Kconfig under
> OMAP Feature Selections. Kevin, Your thoughts on this
>
> config OMAP3430_ENABLE_SPI2_PIN_MUX
> bool "Enable SPI2 pin mux configuration for OMAP3430"
> depends on ARCH_OMAP3430
> default n
> help
> Enable pin mux for SPI2 on OMAP3430 platform. Note
> that the same pins are used for EHCI port2 operation. Hence
> enabling this option effectively disables EHCI port 2
Don't use compile-time setup for this, use runtime. Mux setup is
board-specific and should be done in board init code.
Kevin
--
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
