From: Gregor Boirie <gregor.boirie@parrot.com>
To: <linux-iio@vger.kernel.org>, <paul.cercueil@analog.com>
Subject: libiio and unindexed channel
Date: Mon, 15 Feb 2016 17:13:33 +0100 [thread overview]
Message-ID: <56C1F92D.2020506@parrot.com> (raw)
Hi all,
I hope it is the right place to post for libiio related problems. Please,
forgive my mistakeif it is not.
I'm facing a rather odd problem with unindexed channel (as declared
in ms5611 pressure driver iio_chan_spec 's). libiio does not consider
pressure and temperature channels exposed by the driver as...
channels.
Trying to figure out why, I looked into libiio local backend and found
that:
* on tag v0.6, libiio simply consider unindexed driver channels as
device attribute (see local.c:942) ;
* on actual master, libiio will promote unindexed driver channels to
channels BUT without the scan_element ability (see local.c:1130)
I don't fully understand what real difference it makes but libiio manual
says:
</quote>
a channel that is a scan element is a channel that can generate samples
(for an input channel) or receive samples (for an output channel) after
being enabled.
<quote/>
I feel a bit lost here : I thought input channels were always able to
generate samples. What is this iio_channel_is_scan_element() here
for ? From userspace point of view, what channel indices should be used
for ?
Many thanks in advancefor sharing your time and knowledge.
Regards,
Gregor.
P.S.: by the way, setting the "indexed" field of iio_chan_spec's in
ms5611_core.c makes libiio see temperature and pressure as channels.
next reply other threads:[~2016-02-15 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 16:13 Gregor Boirie [this message]
2016-02-15 16:51 ` libiio and unindexed channel Lars-Peter Clausen
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=56C1F92D.2020506@parrot.com \
--to=gregor.boirie@parrot.com \
--cc=linux-iio@vger.kernel.org \
--cc=paul.cercueil@analog.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.