From: "Hans J. Koch" <hjk@linutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
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: Sun, 14 Jun 2009 22:34:45 +0200 [thread overview]
Message-ID: <20090614203444.GH3639@local> (raw)
In-Reply-To: <4A355155.4020500@grandegger.com>
On Sun, Jun 14, 2009 at 09:36:53PM +0200, Wolfgang Grandegger wrote:
> >>>> if (uioinfo->irq == NO_IRQ)
> >>>> uioinfo->irq = UIO_IRQ_NONE;
> >>> Sorry for my ignorance, but what is NO_IRQ? If I do
>
> It's 0 on PowerPC but ARM seems still to use -1.
Using 0 is simply wrong, especially if people do something like
if (!irq)
return -ERROR;
IRQ number 0 _is_ a valid irq. Maybe not on all platforms, but in generic
code (like UIO) you have to assume it is.
>
> http://lxr.linux.no/linux+v2.6.30/arch/powerpc/include/asm/irq.h#L29
>
> 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...
> 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.
Anyway, if someone fills in an invalid irq in his platform data, he deserves
to crash. No need for that test. UIO docs state that irq is a _required_
element. If you forget to set it, it will probably be 0. On most platforms,
register_irq will fail with that, and you'll notice. If you silently
replace it with UIO_IRQ_NONE, you simply cover up wrong code.
Thanks,
Hans
>
> Wolfgang.
next prev parent reply other threads:[~2009-06-14 20:34 UTC|newest]
Thread overview: 24+ 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-14 12:15 ` Hans J. Koch
2009-06-12 0:04 ` [PATCH 2/2] uio: add an of_genirq driver Wolfram Sang
2009-06-14 12:21 ` Hans J. Koch
2009-06-14 17:14 ` Wolfram Sang
2009-06-14 18:33 ` Hans J. Koch
2009-06-14 19:05 ` Wolfram Sang
2009-06-14 19:23 ` Hans J. Koch
2009-06-14 19:36 ` Wolfgang Grandegger
2009-06-14 20:34 ` Hans J. Koch [this message]
2009-06-14 22:00 ` Wolfram Sang
2009-06-14 23:01 ` Hans J. Koch
2009-06-14 23:46 ` Wolfram Sang
2009-06-14 23:50 ` Hans J. Koch
2009-06-14 19:27 ` Greg KH
2009-06-14 21:46 ` Wolfram Sang
2009-06-14 23:12 ` Alan Cox
2009-06-14 23:45 ` Hans J. Koch
2009-06-15 8:44 ` Alan Cox
2009-06-15 9:45 ` Benjamin Herrenschmidt
2009-06-14 14:40 ` Grant Likely
2009-06-16 9:04 ` Wolfram Sang
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=20090614203444.GH3639@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).