Hello all
How can I call omap_mux_init_signal()
from external driver compiled as module ?
cause the function is not in the standard path include files
and is not exported
regards,
Laurent
Le 11.03.2010 23:48, Tony Lindgren a écrit :
* Peter Barada<peter.barada@xxxxxxxxx> [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 :)
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.
Regards,
Tony
--
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
--
Salutations
Laurent Epinat -> mailto:laurent.epinat@xxxxxxxxxxxxxxx
CIO Informatique
Le millenium
1, rue de Presse - BP 710
42950 Saint-Etienne Cedex 9
Tel 33 (0) 477 93 34 32
Tcopie 33 (0) 477 79 75 55
WWW : http://www.cioinfoindus.fr/
--
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
