public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: IRQ #0 broken on ARM
Date: Sat, 22 Nov 2014 13:55:51 +0100	[thread overview]
Message-ID: <87wq6n4co8.fsf@free.fr> (raw)
In-Reply-To: <CALT56yP6WCnPR3y7-WGzKGS9y+tieR1JUt0wkvOgCPHUy7QVmg@mail.gmail.com> (Dmitry Eremin-Solenikov's message of "Sat, 22 Nov 2014 16:40:13 +0400")

Dmitry Eremin-Solenikov <dbaryshkov@gmail•com> writes:

>>> Perhaps use NR_IRQS_LEGACY here.
>> Ah yes, good idea.
>
> What about using NUM_ISA_INTERRUPTS? This would be logical
> if viper & zeus were converted to call irq_domain_add_legacy_isa.
That would make include/mach/irqs.h depend on include/linux/irqdomain.h.

That's something that makes me fell uneasy, as this irqs.h could be very well
used in assembler files, and I must check it.

On the other hand, NR_IRQS_LEGACY is defined in include/asm/irq.h, and that one
looks a better candidate for inclusion in mach/irqs.h.

Cheers.

-- 
Robert

  reply	other threads:[~2014-11-22 12:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 10:31 IRQ #0 broken on ARM Dmitry Eremin-Solenikov
2014-11-21 10:34 ` Russell King - ARM Linux
2014-11-21 10:51   ` Dmitry Eremin-Solenikov
2014-11-21 10:53   ` Uwe Kleine-König
2014-11-21 10:55     ` Dmitry Eremin-Solenikov
2014-11-21 10:52 ` Marc Zyngier
2014-11-21 11:01   ` Dmitry Eremin-Solenikov
2014-11-21 11:01   ` Russell King - ARM Linux
2014-11-21 11:17     ` Marc Zyngier
2014-11-21 21:32       ` Robert Jarzmik
2014-11-21 22:20         ` Dmitry Eremin-Solenikov
2014-11-21 22:27         ` Rob Herring
2014-11-22 12:18           ` Robert Jarzmik
2014-11-22 12:40             ` Dmitry Eremin-Solenikov
2014-11-22 12:55               ` Robert Jarzmik [this message]
2014-11-21 22:31   ` 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=87wq6n4co8.fsf@free.fr \
    --to=robert.jarzmik@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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