From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Laurent Epinat <laurent.epinat@cioinfoindus.fr>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: beagleboard expansion boards, was Trying to understand how to use new OMAP mux code
Date: Wed, 2 Jun 2010 17:54:56 +0300 [thread overview]
Message-ID: <20100602145456.GC11744@nokia.com> (raw)
In-Reply-To: <20100602144547.GM5980@atomide.com>
On Wed, Jun 02, 2010 at 04:45:48PM +0200, ext Tony Lindgren wrote:
>Yeah having the modules do the platform device init and registration will
>lead into nasty conflicts. The platform device registration really needs
>to happen in the board-*.c files, not in the drivers.
yeah, unless you had a way to register a particular platform_device
conditionaly based on the attached daughter card, but then again, if you
can detect the daughter card, you might as well use that information to
do the muxing correctly on the board-*.c file.
I have to agree modules are not supposed to change platform stuff. On
the other hand, that could be used by EHCI/OHCI to implement port
handoff on runtime:
mux all usb ports to ehci, if enumeration fails, remux ports to ohci
and try again.
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-06-02 14:56 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 [this message]
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=20100602145456.GC11744@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=jhnikula@gmail.com \
--cc=koen@dominion.thruhere.net \
--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).