From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Pavel Roskin <plroskin@gmail.com>, Jonathan Cameron <jic23@kernel.org>
Cc: Jonah Petri <jonah@sense.com>, linux-iio@vger.kernel.org
Subject: Re: Raw data block input: is IIO a good choice?
Date: Wed, 12 Apr 2017 15:36:44 +0100 [thread overview]
Message-ID: <6C2F73E4-E1A9-4F25-9953-D6D8441799DA@jic23.retrosnub.co.uk> (raw)
In-Reply-To: <CAN_72e0zOws-Qusya-yhifbaQ6qDGc5wcOWX+RgT4d0fPpx7-w@mail.gmail.com>
On 12 April 2017 01:05:17 BST, Pavel Roskin <plroskin@gmail.com> wrote:
>Hi Jonathan,
>
>I tried to describe all channels, and it turns out many of them cannot
>be adequately described by the types in iio_chan_type. How do I
>describe the message sequence number?
That wouldn't normally be of interest to userspace as driver would guarantee order.
How about the control register
>value at the time when the data was captured? That data needs to be
>passed to the userspace.
Is it changing on its own? If not normally that is represented via out of band reads of sysfs.
>
>I checked sca3000 driver. I see that it uses
>sca3000_read_first_n_hw_rb() to read the data from the buffer. Can
>that data be accessed by the userspace as is, without any processing?
It is supplied raw to userspace. You can do what you like.
J
>
>Pavel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2017-04-12 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:48 Raw data block input: is IIO a good choice? Pavel Roskin
2017-04-08 0:20 ` 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 [this message]
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=6C2F73E4-E1A9-4F25-9953-D6D8441799DA@jic23.retrosnub.co.uk \
--to=jic23@jic23.retrosnub.co.uk \
--cc=jic23@kernel.org \
--cc=jonah@sense.com \
--cc=linux-iio@vger.kernel.org \
--cc=plroskin@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 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.