From: Lars-Peter Clausen <lars@metafoo.de>
To: Guido Del Vescovo <guido.delvescovo@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"Patil, Rachna" <rachna@ti.com>
Subject: Re: Beaglebone built-in ADC with IIO
Date: Fri, 23 Nov 2012 10:54:25 +0100 [thread overview]
Message-ID: <50AF47D1.3080900@metafoo.de> (raw)
In-Reply-To: <CAE1ao5EKXn_aR_1PE_OyAeFYhYm86AAjAyaRH0yNb8c4fLr0fQ@mail.gmail.com>
Hi,
I added the IIO mailing list and Patil, Rachna, who is the author of the
driver, to Cc.
On 11/23/2012 09:42 AM, Guido Del Vescovo wrote:
> Hi Lars. I'm trying to read the analog inputs of the beaglebone board at an
> higher rate than the one which can be achieved through the *sysfs* method
> (open the file with *fopen*, read a single value with *fscanf*, close the
> file, repeat. C language, of course). In the #beagle IRC channel at
> freenode, I was told to look at the IIO project. I was also told that the
> latest kernel 3.7 for the beaglebone (angstrom distribution) was equipped
> with IIO support for the built-in ADC, but that it is not tested yet. Well,
> I would like to test it. The problem is, I have no idea about how to write
> an hello world application reading data from the analog inputs. I guess I
> should bypass the sysfs and talk directly to the IIO layer, but I'm having
> hard times finding the proper documentation and examples, maybe I'm not
> looking in the right direction.
So yes, there is support for the AM335x ADC in IIO, but not for 3.7. It will
be in 3.8. While IIO provides a character device interface which allows you
to read multiple samples at once, the driver does not implement it yet. So
as it is right now even with IIO you are stuck with reading sysfs files by hand.
- Lars
parent reply other threads:[~2012-11-23 9:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAE1ao5EKXn_aR_1PE_OyAeFYhYm86AAjAyaRH0yNb8c4fLr0fQ@mail.gmail.com>]
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=50AF47D1.3080900@metafoo.de \
--to=lars@metafoo.de \
--cc=guido.delvescovo@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=rachna@ti.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).