From: Tony Lindgren <tony@atomide.com>
To: Laurent Epinat <laurent.epinat@cioinfoindus.fr>
Cc: linux-omap@vger.kernel.org, Jarkko Nikula <jhnikula@gmail.com>
Subject: Re: Trying to understand how to use new OMAP mux code
Date: Thu, 3 Jun 2010 17:06:43 +0300 [thread overview]
Message-ID: <20100603140642.GI30622@atomide.com> (raw)
In-Reply-To: <4C07B136.8010008@cioinfoindus.fr>
* Laurent Epinat <laurent.epinat@cioinfoindus.fr> [100603 16:36]:
>
> I would like one basic configuration for the modules with (twl,net,flash,.. all on the COM's)
> and for the rest, external driver for extra functionalities on the support board.
>
> This is why I need to change the mux pins dynamically by the driver module.
If you really want to do it after the system has booted instead of passing
the desired muxing in the kernel cmdline, you could just do some
shell scripts to echo 0xXXXX > /sys/kernel/debug/omap_mux/whateverpin..
Tony
next prev parent reply other threads:[~2010-06-03 14:06 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
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 [this message]
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=20100603140642.GI30622@atomide.com \
--to=tony@atomide.com \
--cc=jhnikula@gmail.com \
--cc=laurent.epinat@cioinfoindus.fr \
--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).