linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Epinat <laurent.epinat@cioinfoindus.fr>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Trying to understand how to use new OMAP mux code
Date: Wed, 02 Jun 2010 12:09:24 +0200	[thread overview]
Message-ID: <4C062DD4.2050701@cioinfoindus.fr> (raw)
In-Reply-To: <20100311224812.GU2900@atomide.com>

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@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 :)
>
>> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


-- 

Salutations
Laurent Epinat -> mailto:laurent.epinat@cioinfoindus.fr

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-06-02 14:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 22:24 Trying to understand how to use new OMAP mux code Peter Barada
2010-03-11 22:48 ` Tony Lindgren
2010-03-12  4:48   ` Peter Barada
2010-03-12  5:42     ` Premi, Sanjeev
2010-06-02 10:09   ` Laurent Epinat [this message]
2010-06-02 11:21     ` Tony Lindgren
2010-06-02 11:46       ` Jarkko Nikula
2010-06-02 12:56         ` beagleboard expansion boards, was " Koen Kooi
2010-06-02 13:14           ` Jarkko Nikula
2010-06-02 13:57             ` Tony Lindgren
2010-06-02 14:06               ` Koen Kooi
2010-06-02 14:44                 ` Tony Lindgren
2010-06-02 14:14               ` Jarkko Nikula
2010-06-02 14:45                 ` Tony Lindgren
2010-06-02 14:54                   ` Felipe Balbi
2010-06-02 15:01                     ` Tony Lindgren
2010-06-02 16:12                     ` Gadiyar, Anand
2010-06-03 13:42         ` Laurent Epinat
2010-06-03 14:06           ` Tony Lindgren
2010-06-03 14:37             ` Tony Lindgren

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=4C062DD4.2050701@cioinfoindus.fr \
    --to=laurent.epinat@cioinfoindus.fr \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).