public inbox for linux-iio@vger.kernel.org
help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-iio@vger.kernel.org, nuno.sa@analog.com
Subject: iio: Understanding the modes
Date: Wed, 22 Sep 2021 11:22:31 +0200 [thread overview]
Message-ID: <20210922112231.37e565e6@xps13> (raw)
Hello IIO folks,
I am currently writing a blog post trying to explain the situation that
I had with the max1027 driver [1] and possibly try to explain the logic
behind the changes that Jonathan/Nuno requested. As part of this work, I
tried to understand (and explain?) the meaning of the mode definitions
and if they were needed or not, but just looking at the code was not
enough for me to really understand.
While digging into the IIO core, I realized that many definitions and
helpers had no comments explaining their use. I could not find any
documentation about the kernel API in general neither (while the
userspace side is well documented).
I asked yesterday on #linux-iio but got no answers so I am also asking
here in case there are knowledgeable people willing to explain what
each of these definition actually mean and how they should be used:
https://elixir.bootlin.com/linux/latest/source/include/linux/iio/iio.h#L319
I am ready to send a patch upstream to add the necessary comment
so that these explanations do not stay on the mailing list only.
Thanks,
Miquèl
[1] https://lore.kernel.org/linux-iio/20210918180918.6908bbd9@jic23-huawei/
next reply other threads:[~2021-09-22 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 9:22 Miquel Raynal [this message]
2021-09-25 16:08 ` iio: Understanding the modes Jonathan Cameron
2021-09-27 15:29 ` Miquel Raynal
2021-09-30 15:55 ` 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=20210922112231.37e565e6@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=thomas.petazzoni@bootlin.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