linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: magnus.damm@gmail.com (Magnus Damm)
To: linux-arm-kernel@lists.infradead.org
Subject: IRQF_VALID
Date: Thu, 28 Jan 2010 18:34:24 +0900	[thread overview]
Message-ID: <aec7e5c31001280134r50b46b0ay809a125989651197@mail.gmail.com> (raw)

Hi everyone,

I'm trying to understand the idea behind IRQF_VALID. Ideally I'd like
to submit a patch to remove IRQF_VALID to make it easier to share
interrupt code between architectures. Perhaps IRQF_VALID is a left
over from good old times, or maybe it has some hidden use that only
more experienced hackers are aware or. Can anyone please shed some
light?

The ARM default state for interrupts seems to be IRQ_NOREQUEST, so
mach code is required to call the ARM-specific set_irq_flags() even
though most of the interrupt handling code is fairly generic using
CONFIG_GENERIC_HARDIRQS=y. Why this special IRQF_VALID case for ARM?

             reply	other threads:[~2010-01-28  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  9:34 Magnus Damm [this message]
2010-01-28 17:44 ` IRQF_VALID Russell King - ARM Linux
2010-01-29  7:23   ` IRQF_VALID Magnus Damm

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=aec7e5c31001280134r50b46b0ay809a125989651197@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).