All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <plroskin@gmail.com>
To: linux-iio@vger.kernel.org
Subject: Raw data block input: is IIO a good choice?
Date: Fri, 7 Apr 2017 14:48:11 -0700	[thread overview]
Message-ID: <CAN_72e1apsS2nKh7SYiETz+=bJW7mEBS6GV8DmzZEPzroaeACg@mail.gmail.com> (raw)

Hello,

I'm writing a driver for an FPGA device that collects information from
several sensors. The data is collected every 20 milliseconds (i.e. 50
times a second). The data is a 256 byte block that is put to a ring
buffer in the hardware. The software should read the data quickly to
avoid it being overwritten in the ring buffer. It is very important
not to lose any data; previous values are just as important as the
current ones. No parsing needs to be done in the kernel; the userspace
will take care of it.

Is IIO a good choice for such device? I see that the existing IIO
drivers are careful to describe all data they collect. I'm not going
to do that in the kernel (OK, maybe later to allow other utilities to
get the parsed data, but it can be done in userspace too).

I would really appreciate is somebody could point me to a driver that
implements similar functionality.

-- 
Regards,
Pavel Roskin

             reply	other threads:[~2017-04-07 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 21:48 Pavel Roskin [this message]
2017-04-08  0:20 ` Raw data block input: is IIO a good choice? Jonah Petri
2017-04-08  1:47   ` Pavel Roskin
2017-04-08  3:10     ` Jonah Petri
2017-04-08  6:13       ` Pavel Roskin
2017-04-08 14:36         ` Jonathan Cameron
2017-04-11 21:01           ` Pavel Roskin
2017-04-12  0:05             ` Pavel Roskin
2017-04-12 14:36               ` Jonathan Cameron

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='CAN_72e1apsS2nKh7SYiETz+=bJW7mEBS6GV8DmzZEPzroaeACg@mail.gmail.com' \
    --to=plroskin@gmail.com \
    --cc=linux-iio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.