From: shiraz.hashim@st.com (Shiraz HASHIM)
To: linux-arm-kernel@lists.infradead.org
Subject: QUERY: How to handle sharing of interrupt between different peripherals.
Date: Mon, 15 Mar 2010 19:23:18 +0530 [thread overview]
Message-ID: <4B9E3BCE.1060809@st.com> (raw)
In-Reply-To: <20100315111100.GC700@n2100.arm.linux.org.uk>
On 3/15/2010 4:41 PM, Russell King - ARM Linux wrote:
> We do have a system for having a multi-level approach to interrupt decoding.
> Since you have a register which allows you to identify the source of the
> interrupt, I'd recommend for maximum system performance that you use it.
>
> Shared interrupts have the disadvantage that you need to run each handler
> every time a device on the shared interrupt signals, which can be very
> wasteful both in terms of instruction cache lines and IO accesses.
>
> Search arch/arm/ for set_irq_chained_handler to find examples of who to
> deal with multi-level handling of IRQs.
OK. So we need to create virtual irqs (defined by s/w), for shared irqs
which are mapped on to the real irq (defined by the H/W) through
set_irq_chained_handler, right?
thanks for your help.
regards
Shiraz
prev parent reply other threads:[~2010-03-15 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 4:37 QUERY: How to handle sharing of interrupt between different peripherals Viresh KUMAR
2010-03-15 5:18 ` jassi brar
2010-03-15 6:22 ` Ben Dooks
2010-03-15 6:48 ` Viresh KUMAR
2010-03-15 6:44 ` Viresh KUMAR
2010-03-15 6:50 ` jassi brar
2010-03-15 6:55 ` Viresh KUMAR
2010-03-15 7:00 ` jassi brar
2010-03-15 13:04 ` Bill Gatliff
2010-03-15 13:05 ` Bill Gatliff
2010-03-15 11:11 ` Russell King - ARM Linux
2010-03-15 13:53 ` Shiraz HASHIM [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=4B9E3BCE.1060809@st.com \
--to=shiraz.hashim@st.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 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.