All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-parisc@vger.kernel.org, jejb@parisc-linux.org, kyle@mcmartin.ca
Subject: Re: [PATCH] parisc: make NO_IRQ 0 as it should be
Date: Wed, 07 Dec 2011 11:54:17 -0600	[thread overview]
Message-ID: <1323280457.3021.66.camel@dabdike> (raw)
In-Reply-To: <20111206112412.14035.13990.stgit@bob.linux.org.uk>

On Tue, 2011-12-06 at 11:24 +0000, Alan Cox wrote:
> From: Alan Cox <alan@linux.intel.com>
> 
> PA-RISC doesn't use a real IRQ 0 and James says
> 
> "To be honest, we don't care very much.  Parisc interrupts are cascading
> and mostly software assigned (except our EIEM which we keep internal).
> We use a base offset at 16 or 64 (depending on GSC presence or not) so
> IRQs 0-15 aren't legal on parisc either (we frob some of the hard coded
> ISA interrupts on the WAX eisa bus).
> 
> We use NO_IRQ as an IRQ assignment error return and that's about it (and
> that error shouldn't ever really occur)."
> 
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
> 
>  arch/parisc/include/asm/irq.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> 
> diff --git a/arch/parisc/include/asm/irq.h b/arch/parisc/include/asm/irq.h
> index 1073599..fcf6edd 100644
> --- a/arch/parisc/include/asm/irq.h
> +++ b/arch/parisc/include/asm/irq.h
> @@ -10,7 +10,7 @@
>  #include <linux/cpumask.h>
>  #include <asm/types.h>
>  
> -#define NO_IRQ		(-1)
> +#define NO_IRQ		0

Unfortunately, it's not quite as simple as this.  There's one use of
NO_IRQ as an error return in the EIEM code, which returns the internal
line number (which run 0-32/64 ... I'll have to fix those before this
can be done.

James



      reply	other threads:[~2011-12-07 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 11:24 [PATCH] parisc: make NO_IRQ 0 as it should be Alan Cox
2011-12-07 17:54 ` James Bottomley [this message]

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=1323280457.3021.66.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jejb@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    /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.