From: Marcelo Schmitt <marcelo.schmitt@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>, <lars@metafoo.de>,
<Michael.Hennerich@analog.com>, <corbet@lwn.net>,
<marcelo.schmitt1@gmail.com>
Subject: [PATCH v2 0/5] iio: adc: ad4000: Add SPI offload support
Date: Wed, 19 Mar 2025 11:56:51 -0300 [thread overview]
Message-ID: <cover.1742394806.git.marcelo.schmitt@analog.com> (raw)
This patch series extends the ad4000 driver to support SPI offloading.
In addition to that, ad4000 IIO documentation is expanded to:
- list PulSAR parts supported by the ad4000 driver.
- describe some characteristics of AD4000 IIO device.
- describe changes when SPI offload is being used.
v2 changes were tested with ADAQ4003 on CoraZ7 setup running Linux built from
IIO testing branch.
Link to v1: https://lore.kernel.org/linux-iio/cover.1741970538.git.marcelo.schmitt@analog.com/
Change log v1 -> v2
- Fixed passing inappropriate pointer instead of ret to dev_err_probe().
- [new patch] Set transfer bits_per_word to have data in CPU endianness.
- Set iio_dev num_channels close to where channels is set.
- Complement offload message comment about first sample being invalid.
- Documented why the first buffer sample is invalid when offloading.
- Added blank line before a 'simple return'.
Instead of changing bits_per_word according to buffer endianness, I set
bits_per_word for other SPI transfers and updated IIO channels to always use CPU
endianness (the new patch). With that, bits_per_word no longer needs be updated
according to buffer endianness or, in other words, buffer endianness is no
longer related to bits_per_word.
Marcelo Schmitt (5):
iio: adc: ad400: Set transfer bits_per_word to have data in CPU
endianness
iio: adc: ad4000: Add support for SPI offload
Documentation: iio: ad4000: Add new supported parts
Documentation: iio: ad4000: Add IIO Device characteristics section
Documentation: iio: ad4000: Describe offload support
Documentation/iio/ad4000.rst | 86 +++++-
drivers/iio/adc/Kconfig | 7 +-
drivers/iio/adc/ad4000.c | 509 +++++++++++++++++++++++++++++------
3 files changed, 512 insertions(+), 90 deletions(-)
base-commit: af94f401e26f686f7391ce79b38a6129417c22dc
prerequisite-patch-id: 3d517eef53a799adba5922815fe684b913e36773
--
2.47.2
next reply other threads:[~2025-03-19 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 14:56 Marcelo Schmitt [this message]
2025-03-19 14:57 ` [PATCH v2 1/5] iio: adc: ad400: Set transfer bits_per_word to have data in CPU endianness Marcelo Schmitt
2025-03-20 20:43 ` David Lechner
2025-03-21 19:07 ` Marcelo Schmitt
2025-03-19 14:57 ` [PATCH v2 2/5] iio: adc: ad4000: Add support for SPI offload Marcelo Schmitt
2025-03-20 20:47 ` David Lechner
2025-03-21 19:54 ` Marcelo Schmitt
2025-03-21 20:11 ` David Lechner
2025-03-19 14:57 ` [PATCH v2 3/5] Documentation: iio: ad4000: Add new supported parts Marcelo Schmitt
2025-03-20 20:47 ` David Lechner
2025-03-19 14:57 ` [PATCH v2 4/5] Documentation: iio: ad4000: Add IIO Device characteristics section Marcelo Schmitt
2025-03-20 20:47 ` David Lechner
2025-03-19 14:58 ` [PATCH v2 5/5] Documentation: iio: ad4000: Describe offload support Marcelo Schmitt
2025-03-20 20:48 ` David Lechner
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=cover.1742394806.git.marcelo.schmitt@analog.com \
--to=marcelo.schmitt@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.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