From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Sander <tim@krieglstein.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 3.4.28-rt40 arm freescale imx35 pcm43
Date: Wed, 13 Feb 2013 12:59:31 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1302131247260.11905@ionos> (raw)
In-Reply-To: <5977343.5KpmQXLB4x@dabox>
On Wed, 6 Feb 2013, Tim Sander wrote:
> I just noticed that the thread irq/45-IMX-uart is the current thread.
> Nevertheless the interrupt for this thread is enabled which seems wrong to me?
That's wrong indeed. The forced threading masks the interrupt line in
the hard interrupt handling code and keeps it masked. It's unmasked
after the handler thread returns from the interrupt handler function.
> So the interrupt handler imx_rxint does not get call as it is always
> interrupted by the level triggered interrupt of the same hw source?
Right. You have to find the reason, why the interrupt is not disabled
at the interrupt controller level.
Thanks,
tglx
prev parent reply other threads:[~2013-02-13 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:10 3.4.28-rt40 arm freescale imx35 pcm43 Tim Sander
2013-02-06 16:43 ` Tim Sander
2013-02-07 8:57 ` 3.4.28-rt40 arm freescale imx35 pcm43 - patch 86236252d2449313bdbac790023cbc957bf6e426 is cause Tim Sander
2013-02-13 12:13 ` Thomas Gleixner
2013-02-13 17:07 ` Tim Sander
2013-02-13 17:25 ` Thomas Gleixner
2013-02-13 17:40 ` Thomas Gleixner
2013-02-14 15:38 ` [PATCH] 3.4.28-rt40 tglx fix imx.c spinlock Tim Sander
2013-02-14 22:35 ` Thomas Gleixner
2013-02-15 1:13 ` Paul Gortmaker
2013-02-15 7:05 ` [PATHC] 3.6 spinlock fix Tim Sander
2013-02-15 10:18 ` Thomas Gleixner
2013-02-13 11:59 ` Thomas Gleixner [this message]
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=alpine.LFD.2.02.1302131247260.11905@ionos \
--to=tglx@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim@krieglstein.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