linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Williams <john.williams@petalogix.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: gregkh@suse.de,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	hjk@linutronix.de, linuxppc-dev@lists.ozlabs.org
Subject: UIO / of_genirq driver
Date: Thu, 28 Jan 2010 17:13:00 +1000	[thread overview]
Message-ID: <1d3f23371001272313i62fc9158se4cd9173f196fb12@mail.gmail.com> (raw)

Hi,

I came across this thread/patchset from around June last year:

http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/073086.html

where Wolfgang proposed a generic OF-driven UIO driver.  The
discussion seemed to stall after Grant Likely indicated he didn't like
the use of a linux-specific compatible binding in the device tree
(compatible="generic-uio").

I guess I have a couple of questions:

 * did this patchset go anywhere?  I've been using it here the last
few days and it works great.

and more generally:

 * Is there a better way to handle the OF bindings for this sort of thing?

Grant's complaint seems to come up often - when you have generic
controllers in a system (SPI/I2C also spring to mind), we need a way
of signalling somehow to the kernel that each instance has a
particular usage intended.

However, the device-tree guys complain whenever anyone tries to encode
anything non-hardware related into the DTS itself.

I guess I'd like to just open up a discussion, see if there's been any
progress towards a general solution.

Thanks,

John
-- 
John Williams
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663

             reply	other threads:[~2010-01-28  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  7:13 John Williams [this message]
2010-01-28 10:45 ` UIO / of_genirq driver Wolfram Sang
2010-12-03 15:43   ` Stefan Roese
2010-12-03 15:50     ` Wolfram Sang

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=1d3f23371001272313i62fc9158se4cd9173f196fb12@mail.gmail.com \
    --to=john.williams@petalogix.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).