All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: "Hans J. Koch" <hjk@linutronix.de>,
	Wolfgang Grandegger <wg@grandegger.com>,
	devicetree-discuss@ozlabs.org,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 2/2] uio: add an of_genirq driver
Date: Mon, 15 Jun 2009 01:01:36 +0200	[thread overview]
Message-ID: <20090614230135.GI3639@local> (raw)
In-Reply-To: <20090614220022.GB24323@pengutronix.de>

On Mon, Jun 15, 2009 at 12:00:22AM +0200, Wolfram Sang wrote:
> > > For x86 it's not defined at all. But as this code is for the PowerPC,
> > 
> > No, it isn't. What makes you say that? The Kconfig entry doesn't depend
> > on PowerPC. I compiled it on x86...
> 
> It depends on OF. You could compile on x86? Have to check that...

Ooops, forget it. It cannot be selected on x86. I was a bit distracted when
I wrote that, sorry.

> 
> > > where using NO_IRQ seems still to be OK.
> > 
> > No. uio_pdrv_genirq can be used on all platforms, and not all platforms have
> > NO_IRQ. NO_IRQ can be used in platform specific code only.
> 
> Well, the wrapper uses irq_of_parse_and_map(). So far, it returns NO_IRQ if an
> IRQ was not specified (or not found). I could check if there was an
> interrupt-property at all, so I can distinguish between 'not specified' and
> 'not found'. Then, UIO_IRQ_NONE would only be used, if there was none
> specified. Otherwise it will always be the result from irq_of_parse_and_map(),
> whatever that is (even NO_IRQ). Is this what you have in mind?

I would find it better if probe() failed if no irq is specified, printing a
message that tells the user to setup his data correctly before loading the
driver. A user _has_ to setup irq, if there is none, he still has to set
irq=UIO_IRQ_NONE. For that matter, 'not specified' and 'not found' is both
the same bad thing.

Thanks,
Hans

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



WARNING: multiple messages have this Message-ID (diff)
From: "Hans J. Koch" <hjk-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	"Hans J. Koch" <hjk-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
Subject: Re: [PATCH 2/2] uio: add an of_genirq driver
Date: Mon, 15 Jun 2009 01:01:36 +0200	[thread overview]
Message-ID: <20090614230135.GI3639@local> (raw)
In-Reply-To: <20090614220022.GB24323-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On Mon, Jun 15, 2009 at 12:00:22AM +0200, Wolfram Sang wrote:
> > > For x86 it's not defined at all. But as this code is for the PowerPC,
> > 
> > No, it isn't. What makes you say that? The Kconfig entry doesn't depend
> > on PowerPC. I compiled it on x86...
> 
> It depends on OF. You could compile on x86? Have to check that...

Ooops, forget it. It cannot be selected on x86. I was a bit distracted when
I wrote that, sorry.

> 
> > > where using NO_IRQ seems still to be OK.
> > 
> > No. uio_pdrv_genirq can be used on all platforms, and not all platforms have
> > NO_IRQ. NO_IRQ can be used in platform specific code only.
> 
> Well, the wrapper uses irq_of_parse_and_map(). So far, it returns NO_IRQ if an
> IRQ was not specified (or not found). I could check if there was an
> interrupt-property at all, so I can distinguish between 'not specified' and
> 'not found'. Then, UIO_IRQ_NONE would only be used, if there was none
> specified. Otherwise it will always be the result from irq_of_parse_and_map(),
> whatever that is (even NO_IRQ). Is this what you have in mind?

I would find it better if probe() failed if no irq is specified, printing a
message that tells the user to setup his data correctly before loading the
driver. A user _has_ to setup irq, if there is none, he still has to set
irq=UIO_IRQ_NONE. For that matter, 'not specified' and 'not found' is both
the same bad thing.

Thanks,
Hans

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

WARNING: multiple messages have this Message-ID (diff)
From: "Hans J. Koch" <hjk@linutronix.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: devicetree-discuss@ozlabs.org, "Hans J. Koch" <hjk@linutronix.de>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 2/2] uio: add an of_genirq driver
Date: Mon, 15 Jun 2009 01:01:36 +0200	[thread overview]
Message-ID: <20090614230135.GI3639@local> (raw)
In-Reply-To: <20090614220022.GB24323@pengutronix.de>

On Mon, Jun 15, 2009 at 12:00:22AM +0200, Wolfram Sang wrote:
> > > For x86 it's not defined at all. But as this code is for the PowerPC,
> > 
> > No, it isn't. What makes you say that? The Kconfig entry doesn't depend
> > on PowerPC. I compiled it on x86...
> 
> It depends on OF. You could compile on x86? Have to check that...

Ooops, forget it. It cannot be selected on x86. I was a bit distracted when
I wrote that, sorry.

> 
> > > where using NO_IRQ seems still to be OK.
> > 
> > No. uio_pdrv_genirq can be used on all platforms, and not all platforms have
> > NO_IRQ. NO_IRQ can be used in platform specific code only.
> 
> Well, the wrapper uses irq_of_parse_and_map(). So far, it returns NO_IRQ if an
> IRQ was not specified (or not found). I could check if there was an
> interrupt-property at all, so I can distinguish between 'not specified' and
> 'not found'. Then, UIO_IRQ_NONE would only be used, if there was none
> specified. Otherwise it will always be the result from irq_of_parse_and_map(),
> whatever that is (even NO_IRQ). Is this what you have in mind?

I would find it better if probe() failed if no irq is specified, printing a
message that tells the user to setup his data correctly before loading the
driver. A user _has_ to setup irq, if there is none, he still has to set
irq=UIO_IRQ_NONE. For that matter, 'not specified' and 'not found' is both
the same bad thing.

Thanks,
Hans

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

  reply	other threads:[~2009-06-14 23:02 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  0:04 [PATCH 0/2] add OF wrapper for uio-pdrv-genirq Wolfram Sang
2009-06-12  0:04 ` [PATCH 1/2] uio/pdrv_genirq: Refactor probe routine to expose a generic part Wolfram Sang
2009-06-12  0:04   ` Wolfram Sang
2009-06-12  0:04   ` Wolfram Sang
2009-06-14 12:15   ` Hans J. Koch
2009-06-14 12:15     ` Hans J. Koch
2009-06-12  0:04 ` [PATCH 2/2] uio: add an of_genirq driver Wolfram Sang
2009-06-12  0:04   ` Wolfram Sang
2009-06-12  0:04   ` Wolfram Sang
2009-06-14 12:21   ` Hans J. Koch
2009-06-14 12:21     ` Hans J. Koch
2009-06-14 17:14     ` Wolfram Sang
2009-06-14 17:14       ` Wolfram Sang
2009-06-14 17:14       ` Wolfram Sang
2009-06-14 18:33       ` Hans J. Koch
2009-06-14 18:33         ` Hans J. Koch
2009-06-14 18:33         ` Hans J. Koch
2009-06-14 19:05         ` Wolfram Sang
2009-06-14 19:05           ` Wolfram Sang
2009-06-14 19:05           ` Wolfram Sang
2009-06-14 19:23           ` Hans J. Koch
2009-06-14 19:23             ` Hans J. Koch
2009-06-14 19:23             ` Hans J. Koch
2009-06-14 19:36             ` Wolfgang Grandegger
2009-06-14 19:36               ` Wolfgang Grandegger
2009-06-14 19:36               ` Wolfgang Grandegger
2009-06-14 20:34               ` Hans J. Koch
2009-06-14 20:34                 ` Hans J. Koch
2009-06-14 20:34                 ` Hans J. Koch
2009-06-14 22:00                 ` Wolfram Sang
2009-06-14 22:00                   ` Wolfram Sang
2009-06-14 22:00                   ` Wolfram Sang
2009-06-14 23:01                   ` Hans J. Koch [this message]
2009-06-14 23:01                     ` Hans J. Koch
2009-06-14 23:01                     ` Hans J. Koch
2009-06-14 23:46                     ` Wolfram Sang
2009-06-14 23:46                       ` Wolfram Sang
2009-06-14 23:46                       ` Wolfram Sang
2009-06-14 23:50                       ` Hans J. Koch
2009-06-14 23:50                         ` Hans J. Koch
2009-06-14 23:50                         ` Hans J. Koch
2009-06-14 19:27           ` Greg KH
2009-06-14 19:27             ` Greg KH
2009-06-14 21:46             ` Wolfram Sang
2009-06-14 21:46               ` Wolfram Sang
2009-06-14 21:46               ` Wolfram Sang
2009-06-14 23:12     ` Alan Cox
2009-06-14 23:12       ` Alan Cox
2009-06-14 23:12       ` Alan Cox
2009-06-14 23:45       ` Hans J. Koch
2009-06-14 23:45         ` Hans J. Koch
2009-06-14 23:45         ` Hans J. Koch
2009-06-15  8:44         ` Alan Cox
2009-06-15  8:44           ` Alan Cox
2009-06-15  8:44           ` Alan Cox
2009-06-15  9:45       ` Benjamin Herrenschmidt
2009-06-15  9:45         ` Benjamin Herrenschmidt
2009-06-15  9:45         ` Benjamin Herrenschmidt
2009-06-14 14:40   ` Grant Likely
2009-06-14 14:40     ` Grant Likely
2009-06-14 14:40     ` Grant Likely
2009-06-16  9:04     ` Wolfram Sang
2009-06-16  9:04       ` Wolfram Sang
2009-06-16  9:04       ` Wolfram Sang
2009-06-16 12:46       ` Grant Likely
2009-06-16 12:46         ` Grant Likely

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=20090614230135.GI3639@local \
    --to=hjk@linutronix.de \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=magnus.damm@gmail.com \
    --cc=w.sang@pengutronix.de \
    --cc=wg@grandegger.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.