From: "mejjad lahcen" <lmejjad@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: interrupt latency spi
Date: Thu, 3 Apr 2008 09:09:04 -0400 [thread overview]
Message-ID: <9b4863980804030609s3ff05c33g462ffc1769546010@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
hi all of you ,
I am wndering if someone has already done test for interrupt latency on
linx 2.6.23 mpc5200b.
I am working on writing a driver which is get SPi involved on design, and I
know that the spi interrupt will occurs at every 2 us ( speed 4 MHz
interupt occurs when It recieves on bytes) so I am worring about interrupt
latency.
I dont know if someone has any suggestions or a litle advice.
cheers
[-- Attachment #2: Type: text/html, Size: 534 bytes --]
next reply other threads:[~2008-04-03 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:09 mejjad lahcen [this message]
2008-04-03 17:41 ` interrupt latency spi Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2008-04-03 14:04 mejjad lahcen
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=9b4863980804030609s3ff05c33g462ffc1769546010@mail.gmail.com \
--to=lmejjad@gmail.com \
--cc=linuxppc-dev@ozlabs.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).