From: Kevin Hilman <khilman@deeprootsystems.com>
To: Hemanth V <hemanthv@ti.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH][RFC] McSPI Slave and DMA,FIFO support
Date: Mon, 18 May 2009 07:14:53 -0700 [thread overview]
Message-ID: <87y6subiqq.fsf@deeprootsystems.com> (raw)
In-Reply-To: <005201c9d798$46355170$LocalHost@wipultra793> (Hemanth V.'s message of "Mon\, 18 May 2009 14\:38\:55 +0530")
"Hemanth V" <hemanthv@ti.com> writes:
> ----- Original Message -----
> From: "Gadiyar, Anand" <gadiyar@ti.com>
> To: "V, Hemanth" <hemanthv@ti.com>; "Kevin Hilman"
> <khilman@deeprootsystems.com>
>
>
>> >> 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
prev parent reply other threads:[~2009-05-18 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 12:10 [PATCH][RFC] McSPI Slave and DMA,FIFO support Hemanth V
2009-05-15 17:35 ` Kevin Hilman
2009-05-18 7:31 ` Hemanth V
2009-05-18 7:41 ` Gadiyar, Anand
2009-05-18 9:08 ` Hemanth V
2009-05-18 14:14 ` Kevin Hilman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6subiqq.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=gadiyar@ti.com \
--cc=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox