From: Grazvydas Ignotas <notasas@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: multipath mux question
Date: Sat, 3 Jul 2010 00:28:01 +0300 [thread overview]
Message-ID: <AANLkTikb2w3is46Gw-r22F9n2Ockx5rzOWHGo49cnQ8G@mail.gmail.com> (raw)
Hi,
on OMAP3 CBB package GPIO126 can be muxed on 2 pins: mmc1_dat4 and
cam_strobe. On pandora mmc1_dat4 is connected to mmc1 write protect,
this makes omap2_mmc_mux() call omap_mux_init_gpio() on GPIO126, which
muxes both pins and warns:
mux: Multiple gpio paths for gpio126
This results in unusable GPIO. I wonder how should I handle this,
perhaps overriding mux by calling omap_mux_init_signal() after
omap2_hsmmc_init() call? Or maybe omap_mux_init_gpio() should be
patched not to set up GPIOs if it encounters multiple paths?
next reply other threads:[~2010-07-02 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 21:28 Grazvydas Ignotas [this message]
2010-07-05 7:36 ` multipath mux question Tony Lindgren
2010-07-05 11:49 ` Grazvydas Ignotas
2010-07-05 13:10 ` 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=AANLkTikb2w3is46Gw-r22F9n2Ockx5rzOWHGo49cnQ8G@mail.gmail.com \
--to=notasas@gmail.com \
--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).