From: wally bkg <wb666greene-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org
Subject: Long latencies in spidev device driver break real-time performance on Panda/Beagle
Date: Wed, 24 Apr 2013 07:56:41 -0500 [thread overview]
Message-ID: <CANGjJb6FNHyUW5U3=sUMOEpUSuDjCF25a14AxkNDkoBnvjr2qQ@mail.gmail.com> (raw)
I've been trying to run a real-time process to feed a D/A chip using the
spidev driver but am finding the call to /dev/spidevX.Y is responsible for
"random" very long latencies that do not occur if I call the "driver" to
toggle a GPIO pin instead.
My most recent attempts have been with Robert Nelson's 3.9-rc6 kernel for
the Pandaboard ES and he has suggested I contact the OMAP and SPI
maintainers, hence I am sending this message.
Details are here:
http://eewiki.net/display/linuxonarm/PandaBoard_Comments?focusedCommentId=13599653&#comment-13599653
A sample test program that will illustrate the issue can be downloaded
here:
http://eewiki.net/download/attachments/12059008/swave_spidev.c?version=1&modificationDate=1365778735227&api=v2
Robert has run this test code (after changing the GPIO and spidev name
strings for the Beagleboard) and has found the xM is much closer to usable,
but what is curious is that the worst case and number of "missed samples"
are made worse when running as root.
Hoping you have a solution.
--wally.
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
reply other threads:[~2013-04-24 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANGjJb6FNHyUW5U3=sUMOEpUSuDjCF25a14AxkNDkoBnvjr2qQ@mail.gmail.com' \
--to=wb666greene-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).