From: Felix Domke <tmbinc@elitedvb.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 405 Critical Interrupts
Date: Wed, 26 Nov 2003 17:28:37 +0100 [thread overview]
Message-ID: <3FC4D4B5.2030901@elitedvb.net> (raw)
Hi,
i need to have a low-latency interrupt on a 405-based chip with linux 2.4.
Did anybody yet worked on this?
I thought about routing the CriticalInterrupt pretty much the same way
as the HardwareInterrupt, but with disabling MSR_CE. MSR_CE would be
enabled then even in (normal) interrupts, we probably have to add a
__crit_cli and __save_and_crit_cli as someone already suggested.
Does CRIT_EXCEPTION work? Is do_IRQ reentrant? Should i use the same
interrupt processing as a normal hardware interrupt, with the exception
that only "critical"-flagged interrupts are processed?
Any suggestions?
The background: the IBM-STB045xx's capture port, which we use for
IR-decoding, doesn't have any buffering, so when a time-consuming
interrupt is processed (PIO network, maybe PIO ide), we miss IR cycles.
Felix
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-11-26 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 16:28 Felix Domke [this message]
2003-11-26 20:48 ` 405 Critical Interrupts Matt Porter
2003-11-27 2:12 ` Takeharu KATO
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=3FC4D4B5.2030901@elitedvb.net \
--to=tmbinc@elitedvb.net \
--cc=linuxppc-embedded@lists.linuxppc.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).