From: Anand Gadiyar <gadiyar@ti.com>
To: Silesh C V <saileshcv@gmail.com>, linux-omap@vger.kernel.org
Subject: RE: mux init with multiple signal paths.
Date: Thu, 27 Jan 2011 10:10:42 +0530 [thread overview]
Message-ID: <c4a538857557cf1a8a969d99f3140580@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim4hVxEsH3ZkwtEhrhQJ6TP==M5cFZra+oxzrh0@mail.gmail.com>
Silesh C V wrote:
> Hi,
>
> What is the best way to mux signals which are available on
> multiple pins ?
> For example on omap4, gpio 103 can be muxed on
>
> 1.gpmc_ncs6.
> 2.sdmmc_dat1.
>
Specify the signal as pad.signal:
gpmc_ncs6.sdmmc_dat1
(where, pad is the signal name on mode0, and
signal is the signal name for the mode you are interested in).
> omap_mux_init_gpio and omap_mux_init_signal on these pins will now
> return with -EINVAL without modifying the mux register and the pin
> will be left in the state in which the x-loader/u-boot left it at. So
> is it true that the mux framework does not support muxing pins which
> have multiple paths and they have to muxed by accessing the registers
> directly ? Or am I missing something ?
>
The technique above works at least with omap_mux_init_signal.
I'm not so sure about omap_mux_init_gpio.
- Anand
next prev parent reply other threads:[~2011-01-27 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 1:57 mux init with multiple signal paths Silesh C V
2011-01-27 4:40 ` Anand Gadiyar [this message]
2011-01-27 6:10 ` Silesh C V
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=c4a538857557cf1a8a969d99f3140580@mail.gmail.com \
--to=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=saileshcv@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.