From: Michael Welling <mwelling@ieee.org>
To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: BBB IIO ADC access not working
Date: Wed, 19 Aug 2015 16:29:07 -0500 [thread overview]
Message-ID: <20150819212906.GC29773@deathstar> (raw)
In-Reply-To: <782E3A02C2EB2347BEA6DEA69DC7AB86021D3CBD4454@sfamail.SAKURAUS.LOCAL>
On Wed, Aug 19, 2015 at 02:13:10PM -0700, Greg Wilson-Lindberg wrote:
>
> I'm not using /sys/bus/iio/devices/iio:device0/in_voltageX_raw in my program,
> I'm using the iio buffer system.
>
> I tried using cat /sys/bus/iio/devices/iio:device0/in_voltageX_raw while my
> program was running and it worked a couple of times, and got busy a bit also,
> then the touch screen locked up.
This is expected because when the buffer is enabled the device IS busy.
>
> I have not tried to use /sys/bus/iio/devices/iio:device0/in_voltageX_raw from
> in my program, I was hoping for a lighter weight access that didn't require
> so many opens & closes. I'm under the impression that I can only get one
> reading per open if I try to read /sys/bus/iio/devices/iio:device0/in_voltageX_raw.
> Or can I get multiple readings if I do multiple reads.
>
You should be able to keep the file descriptor open and perform multiple reads.
It is necessary lseek before reading from the same channel again.
lseek(fd, 0, SEEK_SET);
You will need a separate file descriptor for each channel.
next prev parent reply other threads:[~2015-08-19 21:29 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 21:15 BBB IIO ADC access not working Greg Wilson-Lindberg
2015-08-05 23:07 ` Greg Wilson-Lindberg
2015-08-06 7:35 ` Daniel Baluta
2015-08-06 15:42 ` Greg Wilson-Lindberg
2015-08-06 18:07 ` Michael Welling
2015-08-10 22:22 ` Greg Wilson-Lindberg
2015-08-10 22:33 ` Michael Welling
2015-08-11 16:00 ` Greg Wilson-Lindberg
2015-08-11 17:02 ` Michael Welling
2015-08-11 17:08 ` Greg Wilson-Lindberg
2015-08-11 17:43 ` Michael Welling
2015-08-13 23:00 ` Greg Wilson-Lindberg
2015-08-14 18:39 ` Michael Welling
2015-08-14 18:43 ` Greg Wilson-Lindberg
2015-08-14 20:40 ` Michael Welling
2015-08-14 23:46 ` Michael Welling
2015-08-18 16:06 ` Greg Wilson-Lindberg
2015-08-18 16:28 ` Michael Welling
2015-08-18 16:54 ` Greg Wilson-Lindberg
2015-08-18 17:37 ` Michael Welling
2015-08-18 17:40 ` Greg Wilson-Lindberg
2015-08-18 18:13 ` Michael Welling
2015-08-18 22:11 ` Greg Wilson-Lindberg
2015-08-18 22:31 ` Michael Welling
2015-08-19 16:27 ` Greg Wilson-Lindberg
2015-08-19 17:52 ` Michael Welling
2015-08-19 20:35 ` Greg Wilson-Lindberg
2015-08-19 20:48 ` Michael Welling
2015-08-19 21:13 ` Greg Wilson-Lindberg
2015-08-19 21:29 ` Michael Welling [this message]
2015-08-19 21:34 ` Greg Wilson-Lindberg
2015-08-19 21:42 ` Michael Welling
2015-08-20 15:50 ` Greg Wilson-Lindberg
2015-08-20 16:14 ` Michael Welling
2015-08-20 16:18 ` Greg Wilson-Lindberg
2015-08-20 17:27 ` Greg Wilson-Lindberg
2015-08-20 17:31 ` Michael Welling
2015-08-20 18:41 ` Greg Wilson-Lindberg
2015-08-20 19:23 ` Michael Welling
2015-08-20 20:21 ` Greg Wilson-Lindberg
2015-08-20 20:48 ` Michael Welling
2015-08-21 17:36 ` Greg Wilson-Lindberg
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=20150819212906.GC29773@deathstar \
--to=mwelling@ieee.org \
--cc=GWilson@sakuraus.com \
--cc=daniel.baluta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox