From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Cc: Devicetree Discussions
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Runtime driver selection for a certain device
Date: Mon, 18 Apr 2011 13:22:18 -0600 [thread overview]
Message-ID: <BANLkTim6Zbh05sO_LpH5RAJUoBFr_=jHLA@mail.gmail.com> (raw)
In-Reply-To: <4DAC8F8A.6060301-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
On Mon, Apr 18, 2011 at 1:22 PM, Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org> wrote:
> Hallo,
>
> I'm looking for a solution for the following problem:
>
> A device may be served by more than one driver depending on the
> application. Therefore the driver to use should be selectable at
> run-time. Lets imaging 4 serial line devices normally handled by the
> Linux serial driver. One of those needs eventually be handled by another
> driver. How could that be realized, especially together with the device
> tree, which is pretty static. Is there a generic way? The bind/unbind
> functions look promising but it's not possible to register more than one
> driver for a device.
Depends on the bus type. I would look at registering the device in
such a way that no driver will bind against it, and then change the
configuration from userspace so the one of the drivers will get bound.
g.
next prev parent reply other threads:[~2011-04-18 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 19:22 Runtime driver selection for a certain device Wolfgang Grandegger
[not found] ` <4DAC8F8A.6060301-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-04-18 19:22 ` Grant Likely [this message]
[not found] ` <BANLkTim6Zbh05sO_LpH5RAJUoBFr_=jHLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-19 16:14 ` Wolfgang Grandegger
[not found] ` <4DADB4D4.1010208-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-04-19 17:25 ` Grant Likely
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='BANLkTim6Zbh05sO_LpH5RAJUoBFr_=jHLA@mail.gmail.com' \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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).