public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	LAK <linux-arm-kernel@lists.arm.linux.org.uk>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 00/32] Convert ARM to generic irq subsystem
Date: Fri, 28 Apr 2006 15:07:53 -0700	[thread overview]
Message-ID: <44529239.2060409@mvista.com> (raw)
In-Reply-To: <20060426230543.GA28908@flint.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Fri, Apr 07, 2006 at 07:45:33PM -0000, Thomas Gleixner wrote:
>> Our patchset, which converts ARM to the generic irq subsystem has 
>> reached a stable state and we ask for inclusion.
> 
> We require people's help on this list concerning these patches.  The
> latest versions can be found at:
> 
>   http://www.tglx.de/projects/armirq/
>   http://www.tglx.de/projects/armirq/2.6.17-rc1/patch-2.6.17-rc1-armirq5.patches.tar.bz2
> 
> (please check for later versions! - note though that www.tglx.de's isp is
> having issues atm.)
> 
> Basically, there's two ways that we can merge these patches:
> 

I am testing these on OMAP.

First pass shows that smc91x interrupts are getting lost.  They are GPIO 
interrupts on most OMAP platforms and pass through a chained gpio handler.  I'm 
still investigating, but I'm guessing it as something to do with SA_TRIGGER_* 
flags used in the smc91x driver for OMAP.

I don't see handling of SA_TRIGGER_* in the generic layer.  Is there a new way 
of handling these?

Kevin

       reply	other threads:[~2006-04-28 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060407095850.690110000@localhost.localdomain>
     [not found] ` <20060426230543.GA28908@flint.arm.linux.org.uk>
2006-04-28 22:07   ` Kevin Hilman [this message]
2006-04-28 22:38     ` [PATCH 00/32] Convert ARM to generic irq subsystem Thomas Gleixner
2006-04-28 23:17       ` Kevin Hilman
2006-04-29 10:08         ` Thomas Gleixner
2006-05-02 11:59           ` Tony Lindgren
2006-05-02 12:33             ` Thomas Gleixner
2006-05-02 18:18               ` Adam Brooks

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=44529239.2060409@mvista.com \
    --to=khilman@mvista.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tglx@linutronix.de \
    /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