From: Pavel Machek <pavel@denx.de>
To: Guenter Roeck <linux@roeck-us.net>
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: Tue, 2 Apr 2013 13:51:51 +0200 [thread overview]
Message-ID: <20130402115151.GA9052@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130402024212.GA19431@roeck-us.net>
On Mon 2013-04-01 19:42:12, Guenter Roeck wrote:
> 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.
Well... one could argue that having "generic-uio" in board's device
tree _is_ wrong, but having driver that binds to "generic-uio" is
not. Hmm?
Or maybe we can do some magic with module parameter. That should be
enough for expected use.
> > 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!
You are welcome :-). Thanks for helping with testing ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-04-02 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 14:23 Pavel Machek
2013-04-01 15:40 ` Pavel Machek
2013-04-02 2:42 ` Guenter Roeck
2013-04-02 11:51 ` Pavel Machek [this message]
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=20130402115151.GA9052@amd.pavel.ucw.cz \
--to=pavel@denx.de \
--cc=dzu@denx.de \
--cc=greg@kroah.com \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=magnus.damm@gmail.com \
--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
all inboxes | Powered by JetHome®