mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: John Williams <john.williams@petalogix.com>
Cc: Michal Simek <monstr@monstr.eu>,
	devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
	linux-kernel@vger.kernel.org, hjk@linutronix.de, gregkh@suse.de
Subject: Re: [PATCH] uio/pdrv_genirq: Add OF support
Date: Thu, 31 Mar 2011 15:23:28 +0200	[thread overview]
Message-ID: <20110331132328.GB2202@pengutronix.de> (raw)
In-Reply-To: <AANLkTi=sG6oVNifwLLi8jjKQXjR6kXZx43NxtFfoPumy@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]


>    Maybe I misunderstand you, in my view it is the responsibility of <vendor>
>    to create their DTS files to indicate they want <special-card1> to bind to
>    generic-uio.

Device tree is a OS-neutral hardware description language. "generic-uio"
is neither OS-neutral nor a hardware description. devicetree.org has
more information about this.

>    Our use-case is pretty clear, in FPGA-based systems it is common to create
>    arbitrary devices that developers just want to control from userspace,
>    with simple IRQ and IO capabilities (DMA can come later :). �They don't
>    need to bind to other kernel APIs or subsystems, and don't want to invest
>    in one-off kernel drivers that simply will never go upstream.

For that, the new_compatible-file would be suitable, I think.

>    UIO is perfect, and simply tagging the device as generic-uio in the DTS is
>    so simple, clean, and elegant.

Simple, yes (I do understand I wrote the first approach ;)) . Elegant,
not really, because it breaks core conventions of the device tree. For
your case it is a very conveniant hack, but it is still a hack.

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2011-03-31 13:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 12:29 UIO " Michal Simek
2011-03-31 12:30 ` [PATCH] uio/pdrv_genirq: Add " Michal Simek
2011-03-31 12:49   ` Wolfram Sang
2011-03-31 13:11     ` John Williams
2011-03-31 13:25       ` Arnd Bergmann
2011-03-31 13:51         ` Michal Simek
2011-03-31 16:34           ` Grant Likely
     [not found]     ` <AANLkTi=sG6oVNifwLLi8jjKQXjR6kXZx43NxtFfoPumy@mail.gmail.com>
2011-03-31 13:23       ` Wolfram Sang [this message]
2011-03-31 13:37         ` Michal Simek
2011-03-31 13:47         ` John Williams
2011-03-31 16:25           ` 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
2011-04-04 17:04                   ` Hans J. Koch
2011-04-04 17:31                     ` Wolfram Sang
2011-04-04 18:24                       ` Hans J. Koch
2011-04-05  6:25                         ` Michal Simek
2011-04-05 11:50                           ` Hans J. Koch
2011-03-31 16:43   ` Grant Likely
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=20110331132328.GB2202@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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®