From: Henk <iio-developer@freedom.nl>
To: linux-iio@vger.kernel.org
Subject: active_scan_mask
Date: Wed, 26 May 2021 20:50:52 +0200 [thread overview]
Message-ID: <08a77a5c-9399-e615-f2df-3251756ed890@freedom.nl> (raw)
Dear all,
I created a custom IIO device in FPGA which in fact contains a bunch of
ADC channels which I can acquire and stream to disk. I use analog
devices' libiio and specifically their iio_readdev application together
with my custom FPGA design and custom iio kernel driver.
Question: what mechanism is updating the indio_dev->active_scan_mask field.
With the iio_readdev application I can add command arguments where I can
activate the channels that I want to retrieve (voltage0 voltage1
...etc). When I use 8 channels as command argument in iio_readdev then
the active_scan_mask seems to be updated with the enabled channels. When
adding even more channels the field is extended. However, when trying to
acquire new data and dropping some of the channel arguments then the
active_scan_mask field does not seem to revert back to the less enabled
(or requested) channels.
So.. I am searching which mechanisms updates that field with the aim to
fix that bug.
Any help is appreciated.
Kind regards
Henk
next reply other threads:[~2021-05-26 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 18:50 Henk [this message]
2021-05-27 9:02 ` active_scan_mask Alexandru Ardelean
2021-05-27 10:06 ` active_scan_mask Henk Medenblik
2021-06-07 10:53 ` active_scan_mask Alexandru Ardelean
2021-06-09 7:03 ` active_scan_mask Henk Medenblik
2021-06-09 8:19 ` active_scan_mask Sa, Nuno
2021-06-09 8:55 ` active_scan_mask Lars-Peter Clausen
2021-06-09 9:37 ` active_scan_mask Henk Medenblik
2021-06-09 13:43 ` active_scan_mask Lars-Peter Clausen
2021-06-09 13:52 ` active_scan_mask Sa, Nuno
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=08a77a5c-9399-e615-f2df-3251756ed890@freedom.nl \
--to=iio-developer@freedom.nl \
--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.