> -----Original Message----- > From: linux-omap-ow...@vger.kernel.org > [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Peter Barada > Sent: Friday, March 12, 2010 10:19 AM > To: Tony Lindgren > Cc: linux-omap@vger.kernel.org > Subject: Re: Trying to understand how to use new OMAP mux code > > On Thu, Mar 11, 2010 at 5:48 PM, Tony Lindgren > <t...@atomide.com> wrote: > > * Peter Barada <peter.bar...@gmail.com> [100311 14:29]: > >> 1) Suppose I want to talk to a bluetooth chip through > UART2. UART2_TX > >> gives me a choice of pins to hook up to, either to pin > AA26 in Mode0, > >> or pin AF5 in Mode1. If I use omape_mux_init_signal("uart2_tx", > >> OMAP_PIN_OUTPUT), which pin will that map to? > > > > You need to check the omap package type you're using to find > > out the correct ball name. If you get lucky, that's already in > > mux34xx.c and you don't need search through the TRMs :) > > The ball name helps me to identify it, but if I understand correctly, > none of the mux code allows the use of a ball name - I have to use the > mode0 name of the ball I want to use (and as you say later qualified > by the signal I want hooked up to that pi), right? > > >> 2) How can I tell the muxing code that I want a specific pin for my > >> UART2_TX signal (that's not a GPIO since those can be directly > >> specified by GPIO number)? > > > > Then you want to use the full signal name: > > > > omap_mux_init_signal("mode0_name.desired_mode", OMAP_PIN_FLAGS) > > > > But as the balls can be separate for each package type, you > > need to figure that out first. > > If my board sets up the balls packaging right (for a 3530 CBB > package), then "omap_mux_init_signal("mcbsp3_clkx.uart2_tx", > OMAP_PIN_OUTPUT);", will setup pin AF5 as mode2, output - thereby > muxing GPIO pin 142 to the UART2_TX signal? > > Next question is for the AM3517 (491 pin), I see the setup for > board-am3517evm int he 2.6.33-rc3 kernel refers to the CBB package > which the comments indicate is a 515 pin package - is this the correct > package to use for the AM3517? Since I have to traverse from my > schematic via ball name to signal name, it helps to know I'm looking > at the right package list. > > Also, it looks like the references in arch/arm/mach-omap2/mux24xx.c to > TI forum URLs (e.g. http://community.ti.com/forums/t/10982.aspx) > takes you to http://e2e.ti.com/support/default.aspx - do you need a > "myTI" login to see that forum message?.
No login is required. It is just that the forum backend has changed and the original link would be leading to a HTTP404 redirecting you to the main page. If we know the original title, search should help in locating the original post. Best regards, Sanjeev > > > > Regards, > > > > Tony > > > > So if I use: omap > -- > To unsubscribe from this list: send the line "unsubscribe > linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
