From: juha.lumme@gmail.com (Juha Lumme)
To: linux-arm-kernel@lists.infradead.org
Subject: Can't get FIQ interrupt to work on i.mx233
Date: Wed, 17 Jul 2013 22:42:26 +0900 [thread overview]
Message-ID: <51E69F42.2060106@gmail.com> (raw)
In-Reply-To: <20130716161643.GB3428@localhost.localdomain>
Hi Dave,
Thanks for the idea, that's indeed a dead simple way to find out.
Being sure that I will get stuck in FIQ handler, I started experimenting
different things, and it seems that if instead of calling
mxs_icoll_set_irq_fiq(31) (which only sets FIQ bit), I directly set bits
4 (FIQ) and 2 (ENABLE) in HW_ICOLL_INTERRUPT31 register, my interrupt
starts working as expected. Maybe I can also leave enable_fiq out this way.
So it currently seems like mxs_icoll_set_irq_fiq (which I patched in)
and enable_fiq (already there) are not working as expected currently in
freescale's mainline 3.10.
I will try to find out the reason, and create patches for this - but if
you have any pointers on what might help me on a right path, I would
appreciate it.
Anyway, thanks for helping me this far already,
Juha
On 07/17/2013 01:16 AM, Dave Martin wrote:
> On Tue, Jul 16, 2013 at 08:44:43PM +0900, Juha Lumme wrote:
>> Hi Russel,
>>
>> Thanks for your reply.
>> And thanks for pointing out the wrong instruction there with the ldr
>> instruction.
>>
>> However, unfortunately the code still doesn't seem to trigger
>> anything (neither to clear the IRQ bit in the timer, nor the GPIO
>> output).. It seems to me as if the handler never gets called. Is
>> there a good way to confirm that any activity is actually triggered
>> when timer3 reaches 0, and the IRQ bit is set to 1 ?
>>
> A brutal, but simple, way to confirm that your handler is being called
> is to try putting an infinite loop in there:
>
> b .
>
> If your board then locks up, the handler is almost certainly getting
> called.
>
> Cheers
> ---Dave
next prev parent reply other threads:[~2013-07-17 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 1:59 Can't get FIQ interrupt to work on i.mx233 Juha Lumme
2013-07-16 8:11 ` Russell King - ARM Linux
2013-07-16 11:44 ` Juha Lumme
2013-07-16 16:16 ` Dave Martin
2013-07-17 13:42 ` Juha Lumme [this message]
2013-07-18 14:19 ` Dave Martin
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=51E69F42.2060106@gmail.com \
--to=juha.lumme@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).