From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: "Hans J. Koch" <hjk@linutronix.de>,
Wolfram Sang <w.sang@pengutronix.de>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
devicetree-discuss@ozlabs.org,
Magnus Damm <magnus.damm@gmail.com>, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 2/2] uio: add an of_genirq driver
Date: Mon, 15 Jun 2009 09:44:49 +0100 [thread overview]
Message-ID: <20090615094449.04b029f0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090614234546.GJ3639@local>
> I did it that way because I saw IRQ 0 in /proc/interrupts on every PC...
>
> >
> > It is the job of the platform to map a physical IRQ 0 to some other
> > representation if it exists outside of arch specific code.
>
> Funny.
>
> > This was
> > decided some years ago and a large part of the kernel simply doesn't
> > support any notion of a real IRQ 0.
>
> Can you tell me the reason for that decision or point me to some ml archive?
The natural C way to write "No xxx" is if (!xxx) hence
if (!dev->irq) {
polling_start();
return 0;
}
The PC "IRQ 0" is the timer - which only appears in the arch code.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 09:44:49 +0100 [thread overview]
Message-ID: <20090615094449.04b029f0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090614234546.GJ3639@local>
> I did it that way because I saw IRQ 0 in /proc/interrupts on every PC...
>
> >
> > It is the job of the platform to map a physical IRQ 0 to some other
> > representation if it exists outside of arch specific code.
>
> Funny.
>
> > This was
> > decided some years ago and a large part of the kernel simply doesn't
> > support any notion of a real IRQ 0.
>
> Can you tell me the reason for that decision or point me to some ml archive?
The natural C way to write "No xxx" is if (!xxx) hence
if (!dev->irq) {
polling_start();
return 0;
}
The PC "IRQ 0" is the timer - which only appears in the arch code.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Hans J. Koch" <hjk@linutronix.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 09:44:49 +0100 [thread overview]
Message-ID: <20090615094449.04b029f0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090614234546.GJ3639@local>
> I did it that way because I saw IRQ 0 in /proc/interrupts on every PC...
>
> >
> > It is the job of the platform to map a physical IRQ 0 to some other
> > representation if it exists outside of arch specific code.
>
> Funny.
>
> > This was
> > decided some years ago and a large part of the kernel simply doesn't
> > support any notion of a real IRQ 0.
>
> Can you tell me the reason for that decision or point me to some ml archive?
The natural C way to write "No xxx" is if (!xxx) hence
if (!dev->irq) {
polling_start();
return 0;
}
The PC "IRQ 0" is the timer - which only appears in the arch code.
Alan
next prev parent reply other threads:[~2009-06-15 8:44 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
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 [this message]
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=20090615094449.04b029f0@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=devicetree-discuss@ozlabs.org \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=magnus.damm@gmail.com \
--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 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.