All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh KUMAR)
To: linux-arm-kernel@lists.infradead.org
Subject: QUERY: How to handle sharing of interrupt between different peripherals.
Date: Mon, 15 Mar 2010 10:07:46 +0530	[thread overview]
Message-ID: <4B9DB99A.5040104@st.com> (raw)

Hello everybody,

In our SOC (SPEArxxx), we have few peripherals which share common interrupt
line. For example we can have GPIO (PL061), SPI (PL022) and SDIO (Arasan) sharing
same physical IRQ line. Now there is a register in SOC which can give status of
this interrupt line (i.e. source of interrupt). We have standard drivers for
all of these, and these drivers don't request IRQ in shared mode.

How should we handle these IRQs now. One way i have been thinking of is to write
a wrapper layer for this type of IRQs for our SOC, which will register actual
IRQ numbers. Standard drivers can be provided virtual IRQ numbers for
registration. Now this wrapper, based on source of interrupt can call the
irq_handler for standard drivers.

Is this approach correct? Or is there any standard way to resolve these issues.

regards,
viresh kumar.

             reply	other threads:[~2010-03-15  4:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  4:37 Viresh KUMAR [this message]
2010-03-15  5:18 ` QUERY: How to handle sharing of interrupt between different peripherals 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

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=4B9DB99A.5040104@st.com \
    --to=viresh.kumar@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.