From: Michael Hennerich <michael.hennerich@analog.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
"jic23@kernel.org" <jic23@kernel.org>,
"federico.vaga@gmail.com" <federico.vaga@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: ZIO wiki analysis of IIO and why it doesn't meet there requirements [was Re: Industrial Input Output analysis]
Date: Tue, 29 Nov 2011 13:54:41 +0100 [thread overview]
Message-ID: <4ED4D611.7030701@analog.com> (raw)
In-Reply-To: <20111129110013.GA27762@mail.gnudd.com>
On 11/29/2011 12:00 PM, Alessandro Rubini wrote:
>
> Hello Lars-Peter, sorry for the delay.
>> We do use IIO for high speed data conversion.
> May I know how high?
>
Hi Alessandro,
Right now we use IIO to capture single work loads at 250MSPS.
User space requests - let's say 1M samples, the IIO driver captures and
returns data to user space.
(sounds a bit similar to your use case)
Hardware is a Virtex6 FPGA, microblaze softcore running Linux and the
converter is a AD9467
on an FMC-LPC card.
The per-sample buffer implementations in IIO are purely optional!
You can build your own buffer implementation by using the
INDIO_BUFFER_HARDWARE flag.
For now the full rate capture is only used for hardware validation
purposes.
Later it is assumed that there will be data decimation inside the FPGA
fabric,
so that only a few MSPS sustained data is DMAed into the processor core
system.
Right now it's not decided whether double buffering or a larger chain is
required in order
to solve the producer-consumer and latency problems.
But I'm pretty optimistic that there is nothing in IIO which prevents me
from getting the
right solution in place.
Ideally there is only one subsytem, and not one targeting low-speed and
another for high speed.
--
Greetings,
Michael
--
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif
next prev parent reply other threads:[~2011-11-29 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH5GJ0qTW_DwaAVhe6ZjGYg=1CPPVuQQn3biyg+2BuYHp1Hefw@mail.gmail.com>
2011-11-27 11:05 ` ZIO wiki analysis of IIO and why it doesn't meet there requirements [was Re: Industrial Input Output analysis] Jonathan Cameron
2011-11-28 11:08 ` Lars-Peter Clausen
2011-11-28 20:14 ` Federico Vaga
2011-11-28 21:29 ` Jonathan Cameron
2011-11-29 7:10 ` Federico Vaga
2011-11-29 17:11 ` Jonathan Cameron
2011-11-29 19:04 ` Federico Vaga
2011-11-29 11:00 ` Alessandro Rubini
2011-11-29 12:54 ` Michael Hennerich [this message]
2011-11-29 14:31 ` Lars-Peter Clausen
2011-11-29 18:05 ` Mark Brown
2011-11-29 14:44 ` Alessandro Rubini
2011-11-30 15:47 ` [Device-drivers-devel] " Getz, Robin
2011-11-30 16:08 ` Hennerich, Michael
2011-11-29 15:17 ` Alessandro Rubini
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=4ED4D611.7030701@analog.com \
--to=michael.hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=federico.vaga@gmail.com \
--cc=greg@kroah.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=rubini@gnudd.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).