mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Michal Simek <monstr@monstr.eu>,
	devicetree-discuss@lists.ozlabs.org, john.williams@petalogix.com,
	linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] uio/pdrv_genirq: Add OF support
Date: Mon, 4 Apr 2011 19:31:49 +0200	[thread overview]
Message-ID: <20110404173149.GB12200@pengutronix.de> (raw)
In-Reply-To: <20110404170437.GA4830@local>

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

Hi Hans,

> > If the generic driver is not sufficent for a user and he
> > patches it, he can simply patch the version string, too?
> 
> Or better write a dedicated driver. Patching a generic thing like uio_pdrv_genirq
> can only be done in specialized drivers in a project. That's hackery that won't
> make it into mainline anyway.

I exactly meant that, maybe didn't make it clear enough. Of course, a seperate
driver would be better, but guess what will happen in most projects.

> > Or can we use the notifiers to set up an individual version? That could also be
> > the place to do special board-setup connected to the selected version.
> 
> How could that look like? If you have an idea for a generic solution, you're
> welcome.

That was more a brainstorming question; there are notifiers which help
populating function-pointers which also can't be expressed in a device-tree.
I just wanted to make sure this approach doesn't get overlooked.

So, the solution for now is to simply add a default value and we can check
later if it can be modified at runtime?

Regards,

   Wolfram

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

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

  reply	other threads:[~2011-04-04 17:31 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
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 [this message]
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=20110404173149.GB12200@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@suse.de \
    --cc=hjk@hansjkoch.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®