From: Thomas Gleixner <tglx@linutronix.de>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com,
LAK <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [PATCH 00/32] Convert ARM to generic irq subsystem
Date: Sat, 29 Apr 2006 00:38:46 +0200 [thread overview]
Message-ID: <1146263927.1322.640.camel@localhost.localdomain> (raw)
In-Reply-To: <44529239.2060409@mvista.com>
On Fri, 2006-04-28 at 15:07 -0700, Kevin Hilman wrote:
> R 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?
No. That chunk got lost unfortunately. Can you retry with the new patch
against -rc3 please ?
http://www.tglx.de/projects/armirq/2.6.17-rc3/patch-2.6.17-rc3-armirq1.patches.tar.bz2
Thanks,
tglx
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2006-04-28 22:38 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 ` [PATCH 00/32] Convert ARM to generic irq subsystem Kevin Hilman
2006-04-28 22:38 ` Thomas Gleixner [this message]
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=1146263927.1322.640.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=khilman@mvista.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap-open-source@linux.omap.com \
/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