From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX & IRQF_ONESHOT
Date: Thu, 13 Jan 2011 22:12:23 +0100 [thread overview]
Message-ID: <4D2F6AB7.30800@eukrea.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1101131839010.2678@localhost6.localdomain6>
On 13/01/2011 19:15, Thomas Gleixner wrote:
> On Thu, 13 Jan 2011, Nicolas Ferre wrote:
>> Le 13/01/2011 10:13, Uwe Kleine-K?nig :
>>> On Thu, Jan 13, 2011 at 09:25:19AM +0100, Eric B?nard wrote:
>>>> Commenting out this line in the ads7846 driver makes it work again.
>>>> Am I missing something obvious or is there a reason for IRQF_ONESHOT
>>>> creating trouble with gpio irq or SPI on i.MX ?
>>> I don't know. Is the irq masked? pending?
>>
>> Just to let you know that I have the same issue on my at91sam9g10ek:
>> atmel_spi + ads7846 (using ADS7843e actually).
>> ... solved by same workaround.
>
> Eric, Nicolas: How are the interrupt handlers set for the relevant
> interrupt lines and how are the interrupt pins configured?
>
on the i.MX27 :
- gpio configured as a plain input (in function ads7846_dev_init() in
arch/arm/mach-imx/eukrea_mbimx27-baseboard.c)
- threaded interrupt handler registered with flags IRQF_TRIGGER_FALLING |
IRQF_ONESHOT (in function ads7846_probe() in drivers/input/touchscreen/ads7846.c)
- the gpio's irq is handled by a chained irq handled registered in
arch/arm/plat-mxc/gpio.c (the CPU has only one real interrupt for all the GPIO
banks so this real IRQ handles up to 5 x 32 gpio's IRQ).
Eric
next prev parent reply other threads:[~2011-01-13 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 9:13 No subject Uwe Kleine-König
2011-01-13 11:12 ` i.MX & IRQF_ONESHOT Nicolas Ferre
2011-01-13 18:15 ` Thomas Gleixner
2011-01-13 21:12 ` Eric Bénard [this message]
2011-01-13 21:24 ` Uwe Kleine-König
2011-01-14 7:35 ` Eric Bénard
2011-01-14 10:57 ` Thomas Gleixner
2011-01-14 13:08 ` Uwe Kleine-König
2011-02-02 21:20 ` Uwe Kleine-König
2011-02-02 21:26 ` Eric Bénard
2011-01-14 11:25 ` Nicolas Ferre
2011-01-14 11:47 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2011-01-13 8:25 Eric Bénard
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=4D2F6AB7.30800@eukrea.com \
--to=eric@eukrea.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.