From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: Regarding hw irq to Linux irq mapping on ARM
Date: Wed, 22 Sep 2010 15:31:21 +1000 [thread overview]
Message-ID: <1285133481.30449.170.camel@pasglop> (raw)
In-Reply-To: <AANLkTinrfJkK85v2epOY95YWaVyMBcxSF2xakHqsM7vh@mail.gmail.com>
On Wed, 2010-09-22 at 00:08 -0300, Grant Likely wrote:
> > Add all the I2C, SPI based irq extenders to that list. They seem to
> > pop up all over the place in rapid speed even in x86. We are happy
> > citizens of the embedded horror^Wuniverse now.
>
> *shudder*
>
> What's the irq handling latency on those? Glad I haven't had to deal
> with any of them yet.
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.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Eric Miao <eric.miao-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Regarding hw irq to Linux irq mapping on ARM
Date: Wed, 22 Sep 2010 15:31:21 +1000 [thread overview]
Message-ID: <1285133481.30449.170.camel@pasglop> (raw)
In-Reply-To: <AANLkTinrfJkK85v2epOY95YWaVyMBcxSF2xakHqsM7vh-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 2010-09-22 at 00:08 -0300, Grant Likely wrote:
> > Add all the I2C, SPI based irq extenders to that list. They seem to
> > pop up all over the place in rapid speed even in x86. We are happy
> > citizens of the embedded horror^Wuniverse now.
>
> *shudder*
>
> What's the irq handling latency on those? Glad I haven't had to deal
> with any of them yet.
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.
Cheers,
Ben.
next prev parent reply other threads:[~2010-09-22 5:31 UTC|newest]
Thread overview: 26+ 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 19:57 ` Grant Likely
2010-09-21 21:45 ` Thomas Gleixner
2010-09-21 21:45 ` Thomas Gleixner
2010-09-22 3:08 ` Grant Likely
2010-09-22 3:08 ` Grant Likely
2010-09-22 5:31 ` Benjamin Herrenschmidt [this message]
2010-09-22 5:31 ` Benjamin Herrenschmidt
2010-09-22 8:59 ` Eric Miao
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
2010-09-27 17:15 ` Mark Brown
2010-09-22 10:51 ` Mark Brown
2010-09-22 10:51 ` Mark Brown
2010-09-22 10:54 ` Mark Brown
2010-09-22 10:54 ` Mark Brown
2010-09-21 22:02 ` Benjamin Herrenschmidt
2010-09-21 22:02 ` Benjamin Herrenschmidt
2010-09-22 3:06 ` Grant Likely
2010-09-22 3:06 ` Grant Likely
2010-09-22 11:00 ` Shaju Abraham
2010-09-22 11:00 ` Shaju Abraham
2010-09-22 11:52 ` Grant Likely
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=1285133481.30449.170.camel@pasglop \
--to=benh@kernel.crashing.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 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.