From: Jarkko Nikula <jhnikula@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Laurent Epinat <laurent.epinat@cioinfoindus.fr>,
linux-omap@vger.kernel.org
Subject: Re: Trying to understand how to use new OMAP mux code
Date: Wed, 2 Jun 2010 14:46:06 +0300 [thread overview]
Message-ID: <20100602144606.4287c438.jhnikula@gmail.com> (raw)
In-Reply-To: <20100602112130.GG5980@atomide.com>
On Wed, 2 Jun 2010 14:21:30 +0300
Tony Lindgren <tony@atomide.com> wrote:
> > 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
>
> You can't that's the whole idea :)
>
> Instead, please do the muxing in the board-*.c file for all the
> pins, or for the device when you initialize the platform data.
>
> The muxing of pins is board specific, and doing it in the board-*.c
> files allows us to free the memory for the unused pin data. Note
> that you can also mux using the kernel cmdline if you have something
> non-standard connected to your board pins.
>
Side note.
How about add-on cards for e.g. BeagleBoard? It would be nice feature
if a kernel module for that particular add-on card can do the muxing
without needing to specify them on cmdline. I.e. if you are switching
between cards there is no need to figure out new cmdline for each of
them. For me even "rootwait" is sometimes too difficult to remember :-)
--
Jarkko
next prev parent reply other threads:[~2010-06-02 11:43 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 [this message]
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=20100602144606.4287c438.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=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).