From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: tricky challenge for getting round level-driven interrupt problem: help!
Date: Wed, 04 May 2005 22:43:35 +0100 [thread overview]
Message-ID: <1115243014.19844.62.camel@localhost.localdomain> (raw)
In-Reply-To: <20050504205831.GF8537@lkcl.net>
On Mer, 2005-05-04 at 21:58, Luke Kenneth Casson Leighton wrote:
> i believe i get it: you raise a level-triggered interrupt which _stays_
> raised until such time as your fifo is empty.
Bingo. It only goes away when the chip really has nothing left to say.
> all - that sometimes (frequently, in fact - about 1 in every
> 50 times) it hasn't got round to clearing the level-driven
> interrupt by the time we come out of the ARM ISR (!)
So you'll poll again and find there is no pending work to do.
> hence the redesign to do alternate read-write-read-write, and making
> reads exclusive of writes, etc.
and maybe even turn the IRQ off and use a timer if its slow and not
sensitive to latency.. ?
> ... so - in your opinion, alan, is the old approach we had
> actually _on_ the right lines?
level triggered IRQ does sort of expect the other end responds promptly
to be efficient as opposed to merely reliable.
> also, are you going to ukuug in august, it being _in_
> aberystwyth and all :)
Its not in Aberystwyth, but I might be. Its in Swansea 8)
next prev parent reply other threads:[~2005-05-04 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:56 Luke Kenneth Casson Leighton
2005-05-04 1:50 ` Alan Cox
2005-05-04 20:58 ` Luke Kenneth Casson Leighton
2005-05-04 21:43 ` Alan Cox [this message]
2005-05-04 23:20 ` Luke Kenneth Casson Leighton
2005-05-05 11:32 ` Luke Kenneth Casson Leighton
2005-05-06 10:57 ` Luke Kenneth Casson Leighton
2005-05-08 12:32 ` Luke Kenneth Casson Leighton
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=1115243014.19844.62.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
/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®