public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Pavel Machek <pavel@denx.de>
Cc: sr@denx.de, w.sang@pengutronix.de, magnus.damm@gmail.com,
	hjk@linutronix.de, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, dzu@denx.de
Subject: Re: UIO device tree bindings.
Date: Mon, 1 Apr 2013 19:42:12 -0700	[thread overview]
Message-ID: <20130402024212.GA19431@roeck-us.net> (raw)
In-Reply-To: <20130401154008.GA20963@amd.pavel.ucw.cz>

On Mon, Apr 01, 2013 at 05:40:08PM +0200, Pavel Machek wrote:
> On Mon 2013-04-01 16:23:36, Pavel Machek wrote:
> > Hi!
> > 
> > I'd like to get uio device tree bindings to work -- with recent FPGA
> > parts it will be important. Latest version I see is 
> > 
> > https://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/073087.html
> > 
> > ... Is there anything newer?
> > 
> > I red the discussion, and main problem seems to be the "tell kernel to
> > drive this device tree device", right?
> 
Problem seems to be the notion that the proposed devicetree entry would not
describe the hardware, but its use. Not really sure I understand the problem,
as I would see the hardware description to be "A hardware device which is
compatible to and managed by the generic-uio driver". I would argue that
this _is_ a hardware description (if not, what is ?), but I am not the one
to make the call.

> So... here's the port to recent kernels. Not for mainline.
> 
> Signed-off-by: Pavel Machek <pavel@denx.de>
> 
Turns out this is exactly what I need, and your post saves me the time
I would have spent writing essentially the same code and submitting it,
only to have it rejected.

Thanks a lot for digging this up!

Guenter

  reply	other threads:[~2013-04-02  2:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 14:23 UIO device tree bindings Pavel Machek
2013-04-01 15:40 ` Pavel Machek
2013-04-02  2:42   ` Guenter Roeck [this message]
2013-04-02 11:51     ` Pavel Machek
2013-04-02 12:51       ` Guenter Roeck
2013-04-02 13:19         ` Pavel Machek
2013-04-02 13:46           ` Pavel Machek
2013-04-02 15:43             ` Guenter Roeck
2013-04-02 20:35               ` Pavel Machek

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=20130402024212.GA19431@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dzu@denx.de \
    --cc=greg@kroah.com \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=pavel@denx.de \
    --cc=sr@denx.de \
    --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