From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: QUERY: How to handle sharing of interrupt between different peripherals.
Date: Mon, 15 Mar 2010 16:00:03 +0900 [thread overview]
Message-ID: <1b68c6791003150000s4417e982ofa7dc2998575bd67@mail.gmail.com> (raw)
In-Reply-To: <4B9DD9F0.60603@st.com>
On Mon, Mar 15, 2010 at 3:55 PM, Viresh KUMAR <viresh.kumar@st.com> wrote:
> Second: Now UART, SDIO, SPI, I2S all have a common interrupt line, this is what
> we need to handle. For this IRQF_SHARED is a better way.
ok, I misunderstood.
next prev parent reply other threads:[~2010-03-15 7:00 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 [this message]
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
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=1b68c6791003150000s4417e982ofa7dc2998575bd67@mail.gmail.com \
--to=jassisinghbrar@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).