From: Gabriel Paubert <paubert@iram.es>
To: mejjad lahcen <lmejjad@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: interrupt latency spi
Date: Thu, 3 Apr 2008 19:41:23 +0200 [thread overview]
Message-ID: <20080403174123.GA25888@iram.es> (raw)
In-Reply-To: <9b4863980804030609s3ff05c33g462ffc1769546010@mail.gmail.com>
On Thu, Apr 03, 2008 at 09:09:04AM -0400, mejjad lahcen wrote:
> 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.
Expecting to be able to handle an interrupt every 2 microseconds is
simply crazy. Your hardware should at least have some FIFO to buffer
the data, hey, that's what UART started doing even at much lower bit
rates...
Gabriel
next prev parent reply other threads:[~2008-04-03 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:09 interrupt latency spi mejjad lahcen
2008-04-03 17:41 ` Gabriel Paubert [this message]
-- 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=20080403174123.GA25888@iram.es \
--to=paubert@iram.es \
--cc=linuxppc-dev@ozlabs.org \
--cc=lmejjad@gmail.com \
/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).