From: Oezguen Guenyeli <oezguen.guenyeli.wg@renesas.com>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Problem about Read Multiple Raw Function
Date: Tue, 26 Nov 2019 12:56:11 +0000 [thread overview]
Message-ID: <OSBPR01MB2326981343F90B11AB6CA23DB1450@OSBPR01MB2326.jpnprd01.prod.outlook.com> (raw)
Hi,
I am developing Linux iio driver for one sensor and sensor provides 15 measurement samples that have to been sent the user-space for high level algorithm.
I can read data from dev/iio:device and I can apply high-level algorithm. However, I have problem about read_raw_multi function. Max_len pass value as INDIO_MAX_RAW_ELEMENTS in iio_read_channel_info function that locates in industrialio-core.c file and INDIO_MAX_RAW_ELEMENTS is defined 4 in iio.h file.
Is there any specific reason to define 4 ? Because in that way I cannot pass 15 values to user space with read_raw_multi function.
Thanks,
Özgün Kemal Günyeli
next reply other threads:[~2019-11-26 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:56 Oezguen Guenyeli [this message]
2019-11-26 15:16 ` Problem about Read Multiple Raw Function Jonathan Cameron
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=OSBPR01MB2326981343F90B11AB6CA23DB1450@OSBPR01MB2326.jpnprd01.prod.outlook.com \
--to=oezguen.guenyeli.wg@renesas.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;
as well as URLs for NNTP newsgroup(s).