From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: linux-kernel@vger.kernel.org,
Linux ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: disabling "double-calling" of level-driven interrupts
Date: Sat, 7 May 2005 21:32:12 +0100 [thread overview]
Message-ID: <20050507203212.GG17194@lkcl.net> (raw)
hi, please respond cc direct, thank you.
a kind response from alan alerted me to investigate some issues
that we are having with the skyminder (arm 720 cirrus logic
"maverick" EDB7134 whatever).
something he said made me go "twitch" - the infrastructure involving
interrupts in the 2.6 kernel - that they can be called TWICE.
well, that's exactly what i am seeing happen - even when the
relevant INTSR1 bit is clear.
at the top of the interrupt service routine, i double-check the
bit of INTSR1 that caused the interrupt.
i find it to be clear.
doing an immediate return IRQ_HANDLED results in working code,
whereas before, the behaviour of our LCD was utterly unreliable.
[we have a communications protocol to a PIC, over the 8-bit port,
indicating where and what the PIC is to blop onto the LCD screen.
the protocol is variable-length-encoded: if it gets screwed,
for example by a double-interrupt adding in an extra character...]
so.
i have some questions.
1) _why_ am i getting double-interrupts, even under circumstances
where i double-check the relevant INTSR1 bit and ONLY drop out
of the interrupt service routine once that bit is cleared?
2) is there something i am supposed to do, some function i
am supposed to call, which stops the interrupt handler from
being double-called?
3) could i have got something wrong, is there some interrupt
function i am supposed to write, which is _supposed_ to check
for this condition?
4) could there be something missing from the CLPS711x irq.c which
is supposed to be there?
5) other
many thanks for any assistance.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
next reply other threads:[~2005-05-07 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 20:32 Luke Kenneth Casson Leighton [this message]
2005-05-08 0:31 ` Grant Coady
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=20050507203212.GG17194@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®