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: [PATCH V2] ST SPEAr: Adding support for shared irq layer
Date: Mon, 03 May 2010 10:20:02 +0530	[thread overview]
Message-ID: <4BDE55FA.2010207@st.com> (raw)
In-Reply-To: <20100501095649.GD12172@n2100.arm.linux.org.uk>

On 5/1/2010 3:26 PM, Russell King - ARM Linux wrote:
> On Fri, Apr 30, 2010 at 11:28:06AM +0530, Viresh KUMAR wrote:
>> On 4/27/2010 5:30 PM, Viresh KUMAR wrote:
>>> Multiple peripherals in SPEAr share common hardware interrupt lines.
>>> This patch adds support for a shared irq layer, which registers hardware
>>> irqs by itself and exposes virtual irq numbers to peripherals.
>>>
>>> Modifications in V2:
>>> - use get_irq_data instead of get_irq_chip_data
>>> - add support for enabling and clearing interrupt based on machine specific
>>>   implementation. (i.e. It may be required to set/reset a bit in different
>>>   machines for enabling/clearing interrupt.)
>>> - Modified shirq related structures in spear320.c
>>>
>>> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
>>
>> If this patch looks fine, can i send this to russell's patch system.
> 
> Patch looks fine - my only concern is that the IRQ subsystem isn't used
> to decode things like serial status register interrupts.  It's supposed
> to be used to decode the interrupt using the interrupt controllers only.
> 

Russell,

I didn't understood your point clearly. Few weeks back i raised this query
in LKML, and you suggested to implement this layer using irq_chained_handlers.
And this is how it is done in multiple platforms, and GPIO everywhere.

Should i implement it some other way?

viresh.

  reply	other threads:[~2010-05-03  4:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 12:00 [PATCH V2] ST SPEAr: Adding support for shared irq layer Viresh KUMAR
2010-04-30  5:58 ` Viresh KUMAR
2010-05-01  9:56   ` Russell King - ARM Linux
2010-05-03  4:50     ` Viresh KUMAR [this message]
2010-05-03  8:10       ` Russell King - ARM Linux

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=4BDE55FA.2010207@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.