From: Wolfgang Denk <wd@denx.de>
To: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8260 MCC Interrupt priority
Date: Mon, 09 Sep 2002 21:36:56 +0200 [thread overview]
Message-ID: <20020909193701.AABCDFA8B@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 09 Sep 2002 18:47:08 +0200." <020c01c25820$89c23880$0700a8c0@pc005>
Dear Gianfranco,
in message <020c01c25820$89c23880$0700a8c0@pc005> you wrote:
>
> I'm currently working on a custom board derived from EST8260. We are trying
> to implement a device driver of MCC to control the interface with a
> synchrounous PCM.
> I have noted that when there is an interrupt on SCC1 (or FCCx) the latency
> time of MCC interrupt increase. Now I'm really concerned about the
> possibility to loose some frame due to an heavy use of such interfaces.
If losing a frame is _that_ critical to you yoy should consider using
RTAI.
> Do anybody knows if there is the possibility to avoid such behaviour (maybe
> allowing an interrupt casting with the MCC ISR)?
With RTAI you can register the MCC as a real-time interrupt which has
higher priority than all Linux stuff, guaranteed.
See http://www.rtai.org/ , and feel free to contact me when you need
help.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The software required `Windows 95 or better', so I installed Linux.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-09 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 16:47 8260 MCC Interrupt priority Ing.Gianfranco Morandi
2002-09-09 19:36 ` Wolfgang Denk [this message]
2002-09-10 17:00 ` Ing.Gianfranco Morandi
2002-09-10 18:12 ` Wolfgang Denk
2002-09-10 0:00 ` Dan Brennan
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=20020909193701.AABCDFA8B@denx.denx.de \
--to=wd@denx.de \
--cc=gianfranco.morandi@euro-studio.it \
--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).