From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Discuss"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: multiple drivers for same hardware
Date: Fri, 13 Jan 2012 09:21:09 -1000 [thread overview]
Message-ID: <4F108425.80607@firmworks.com> (raw)
In-Reply-To: <316952FA-B163-46F8-B4B5-8CC0B97EAEB9-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
On 1/13/2012 8:52 AM, Kumar Gala wrote:
> We have some scenarios in which we might have 2 different drivers (one in kernel or one user space as an example) and wanted to see how we'd convey in the device tree which driver should "claim" the specific device instance.
>
> From glancing at the OF specs it seems we could utilize the precedence order of compatible as a means to specify. So something like:
>
> [ bind with UIO instead of standard driver ]
>
> compatible = "gianfar-lnx-uio", "gianfar";
>
> vs [ bind with stock kernel driver ]
> compatible = "gianfar";
That is certainly the standard way of doing it.
>
> The other thought I had was introducing a new property like:
>
> linux-drv = "gianfar-uio";
> compatible = "gianfar";
>
> thoughts?
Why add a new mechanism when there is an existing one that does what you
want?
>
> - k
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
next prev parent reply other threads:[~2012-01-13 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:52 multiple drivers for same hardware Kumar Gala
[not found] ` <316952FA-B163-46F8-B4B5-8CC0B97EAEB9-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2012-01-13 19:21 ` Mitch Bradley [this message]
2012-01-16 16:21 ` Stuart Yoder
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=4F108425.80607@firmworks.com \
--to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@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).