linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Barada <peter.barada@gmail.com>
To: linux-omap@vger.kernel.org
Subject: Trying to understand how to use new OMAP mux code
Date: Thu, 11 Mar 2010 17:24:31 -0500	[thread overview]
Message-ID: <738b3f7e1003111424t34326158j570980c691a98853@mail.gmail.com> (raw)

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?

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)?


Thanks in advance!

             reply	other threads:[~2010-03-11 22:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 22:24 Peter Barada [this message]
2010-03-11 22:48 ` Trying to understand how to use new OMAP mux code Tony Lindgren
2010-03-12  4:48   ` Peter Barada
2010-03-12  5:42     ` Premi, Sanjeev
2010-06-02 10:09   ` Laurent Epinat
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=738b3f7e1003111424t34326158j570980c691a98853@mail.gmail.com \
    --to=peter.barada@gmail.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;
as well as URLs for NNTP newsgroup(s).