devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Michal Simek <monstr@monstr.eu>
Cc: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
	john.williams@petalogix.com, linux-kernel@vger.kernel.org,
	hjk@hansjkoch.de, w.sang@pengutronix.de, arnd@arndb.de
Subject: Re: [PATCH v3] uio/pdrv_genirq: Add OF support
Date: Mon, 18 Apr 2011 19:35:13 +0900	[thread overview]
Message-ID: <20110418103513.GA27864@linux-sh.org> (raw)
In-Reply-To: <1303116654-5042-1-git-send-email-monstr@monstr.eu>

On Mon, Apr 18, 2011 at 10:50:54AM +0200, Michal Simek wrote:
> Adding OF binding to genirq.
> Version string is setup to the "devicetree".
> 
> Compatible string is not setup for now but you can add your
> custom compatible string to uio_of_genirq_match structure.
> 
> For example with "uio" compatible string:
> static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
> 	{ .compatible = "uio", },
> 	{ /* empty for now */ },
> };
> 
> Signed-off-by: Michal Simek <monstr@monstr.eu>
> 
Perhaps a silly question, but how are you planning on differentiating
between uio_pdrv and uio_pdrv_genirq binding if someone has both enabled?

uio_pdrv obviously doesn't have OF bindings at the moment, but it seems
like you could easily parse the memory ranges in addition to the IRQ and
come up with a generic binding that would work for both.

We also have a shiny new Documentation/devicetree these days, so it would
be nice to see the binding documented at the same time.

  reply	other threads:[~2011-04-18 10:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  8:50 [PATCH v3] uio/pdrv_genirq: Add OF support Michal Simek
2011-04-18 10:35 ` Paul Mundt [this message]
     [not found]   ` <20110418103513.GA27864-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>
2011-04-18 11:10     ` Michal Simek
     [not found] ` <1303116654-5042-1-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-04-18 16:06   ` Wolfram Sang
     [not found]     ` <20110418160658.GD23814-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-04-19  1:58       ` John Williams
2011-04-19  6:11         ` Grant Likely
2011-04-19  7:32           ` Arnd Bergmann
     [not found]             ` <201104190932.31777.arnd-r2nGTMty4D4@public.gmane.org>
2011-04-19  8:42               ` Michal Simek
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
     [not found]                 ` <201104191707.40456.arnd-r2nGTMty4D4@public.gmane.org>
2011-04-19 15:45                   ` Grant Likely
     [not found]         ` <BANLkTimFnfgiQ5aMq_KwqHP8p92pjOJJwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-21 12:08           ` Wolfram Sang
     [not found]             ` <20110421120855.GC2135-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
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=20110418103513.GA27864@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --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;
as well as URLs for NNTP newsgroup(s).