From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: "Hans J. Koch" <hjk-vqZO0P4V72/QD6PfKP4TzA@public.gmane.org>
Cc: gregkh-l3A5Bk7waGM@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
hjk-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org
Subject: Re: [PATCH] uio/pdrv_genirq: Add OF support
Date: Sat, 2 Apr 2011 12:35:50 +0200 [thread overview]
Message-ID: <20110402103550.GA21760@pengutronix.de> (raw)
In-Reply-To: <20110331203024.GE2734@local>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
> For UIO, it is not enough to just know "we have this chip using that driver",
> at least not for a generic driver like the one proposed in this patch.
So, what about setting this string to a default (e.g. '0' or 'generic' or
whatever). Then, userspace knows this is the unmodified upstream version of the
generic driver. If the generic driver is not sufficent for a user and he
patches it, he can simply patch the version string, too?
Or can we use the notifiers to set up an individual version? That could also be
the place to do special board-setup connected to the selected version.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2011-04-02 10:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 12:29 UIO OF support Michal Simek
[not found] ` <1301574600-4861-1-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-03-31 12:30 ` [PATCH] uio/pdrv_genirq: Add " Michal Simek
[not found] ` <1301574600-4861-2-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-03-31 12:49 ` Wolfram Sang
[not found] ` <20110331124925.GA2202-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-03-31 13:10 ` John Williams
[not found] ` <AANLkTi=sG6oVNifwLLi8jjKQXjR6kXZx43NxtFfoPumy-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-31 13:23 ` Wolfram Sang
[not found] ` <20110331132328.GB2202-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-03-31 13:37 ` Michal Simek
2011-03-31 13:47 ` John Williams
[not found] ` <AANLkTikCEYK5K3sQ1rgVK6qMvizQYUn=xsiSPedNRn9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-31 16:25 ` Grant Likely
2011-03-31 13:11 ` John Williams
[not found] ` <AANLkTinJrG=s3Xuvf_=bNtYF-z8u+YXvd217UKKz24ik-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-31 13:25 ` Arnd Bergmann
2011-03-31 13:51 ` Michal Simek
2011-03-31 16:34 ` Grant Likely
2011-03-31 13:28 ` Michal Simek
2011-03-31 17:03 ` Hans J. Koch
2011-03-31 17:57 ` Michal Simek
2011-03-31 19:23 ` Hans J. Koch
2011-03-31 19:48 ` Grant Likely
2011-03-31 20:30 ` Hans J. Koch
2011-04-02 10:35 ` Wolfram Sang [this message]
[not found] ` <20110402103550.GA21760-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-04-04 17:04 ` Hans J. Koch
2011-04-04 17:31 ` Wolfram Sang
[not found] ` <20110404173149.GB12200-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-04-04 18:24 ` Hans J. Koch
2011-04-05 6:25 ` Michal Simek
[not found] ` <4D9AB5E8.3080401-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-04-05 11:50 ` Hans J. Koch
2011-03-31 16:43 ` Grant Likely
[not found] ` <20110331164348.GI26709-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-03-31 17:54 ` 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=20110402103550.GA21760@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=hjk-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=hjk-vqZO0P4V72/QD6PfKP4TzA@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).