linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Regarding hw irq to Linux irq mapping on ARM
Date: Sun, 26 Sep 2010 00:08:57 +0100	[thread overview]
Message-ID: <4C9E8109.2000408@fluff.org> (raw)
In-Reply-To: <20100924150608.GB30666@sirena.org.uk>

On 24/09/10 16:06, Mark Brown wrote:
> On Fri, Sep 24, 2010 at 12:45:32AM +0100, Ben Dooks wrote:
>> On 22/09/10 09:59, Eric Miao wrote:
> 
>>>> And i2c in many cases want to be called from sleep'able context... might
>>>> be a good idea to restrict some of these to threaded interrupts. A whole
>>>> different discussion I suppose.
> 
>> The i2c case, it is generally the code decoding the interrupt that needs
>> to do this, and is part of the i2c specific driver, and is written as
>> some form of thread or work-queue.
> 
> The standard thing these days is a threaded IRQ handler.

Yes, however my first point was really do we care the method
for the interrupt's detection when talking about mapping them?

  reply	other threads:[~2010-09-25 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=6nCJnfLB1uc0uLGOvOm0CX_R=j-8GQWTzmmep@mail.gmail.com>
2010-09-21 19:57 ` Regarding hw irq to Linux irq mapping on ARM Grant Likely
2010-09-21 21:45   ` Thomas Gleixner
2010-09-22  3:08     ` Grant Likely
2010-09-22  5:31       ` Benjamin Herrenschmidt
2010-09-22  8:59         ` Eric Miao
2010-09-23 23:45           ` Ben Dooks
2010-09-24 15:06             ` Mark Brown
2010-09-25 23:08               ` Ben Dooks [this message]
2010-09-27 17:15                 ` Mark Brown
2010-09-22 10:51       ` Mark Brown
2010-09-22 10:54         ` Mark Brown
2010-09-21 22:02   ` Benjamin Herrenschmidt
2010-09-22  3:06     ` Grant Likely
2010-09-22 11:00     ` Shaju Abraham
2010-09-22 11:52       ` 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=4C9E8109.2000408@fluff.org \
    --to=ben-linux@fluff.org \
    --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).