From: Grant Likely <grant.likely@secretlab.ca>
To: Arnd Bergmann <arnd@arndb.de>
Cc: John Williams <john.williams@petalogix.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Michal Simek <monstr@monstr.eu>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, hjk@hansjkoch.de
Subject: Re: [PATCH v3] uio/pdrv_genirq: Add OF support
Date: Tue, 19 Apr 2011 09:45:10 -0600 [thread overview]
Message-ID: <BANLkTim9_n85ahW781fGjf_iofhBjnD36w@mail.gmail.com> (raw)
In-Reply-To: <201104191707.40456.arnd@arndb.de>
On Tue, Apr 19, 2011 at 9:07 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 19 April 2011, Grant Likely wrote:
>> > or whatever, as this would bind all instances matching vendor,device.
>> >
>> > So, the question I have is, how to handle bind per-instance?
>>
>> By manipulating a property on the device instance of course! :-)
>>
>> Something like: echo "generic-uio" >>
>> /sys/devices/path/to/device/a-property-that-changes-the-driver-it-will-bind-to.
>>
>
> But what code would create that in sysfs, and based on what properties
> of the device? Should we do that for every platform device, or perhaps
> for every one that has any resources?
Yes, I think it can be a generic facility for all platform_devices.
We already have some code to support user-space manipulated driver
binding/unbinding. This is very much in the same vein.
g.
next prev parent reply other threads:[~2011-04-19 15:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 8:50 Michal Simek
2011-04-18 10:35 ` Paul Mundt
2011-04-18 11:10 ` Michal Simek
2011-04-18 16:06 ` Wolfram Sang
2011-04-19 1:58 ` John Williams
2011-04-19 6:11 ` Grant Likely
2011-04-19 7:32 ` Arnd Bergmann
2011-04-19 12:37 ` John Williams
2011-04-19 13:02 ` Arnd Bergmann
2011-04-19 14:49 ` Grant Likely
2011-04-19 15:07 ` Arnd Bergmann
2011-04-19 15:45 ` Grant Likely [this message]
2011-04-21 12:08 ` Wolfram Sang
2011-04-21 23:46 ` John Williams
2011-04-22 6:07 ` Wolfram Sang
2011-04-19 8:16 ` Michal Simek
2011-04-19 6:08 ` Grant Likely
2011-04-19 8:15 ` Michal Simek
2011-04-19 22:00 ` Hans J. Koch
2011-04-19 23:09 ` Scott Wood
2011-04-27 11:05 ` Michal Simek
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=BANLkTim9_n85ahW781fGjf_iofhBjnD36w@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hjk@hansjkoch.de \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®