From: David Lechner <dlechner@baylibre.com>
To: "Angelo Dureghello" <adureghello@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: ad7380: add support for SPI offload
Date: Sat, 22 Feb 2025 11:31:01 -0600 [thread overview]
Message-ID: <7b64c6a9-0606-45ba-be45-7ae11c4fdf39@baylibre.com> (raw)
In-Reply-To: <20250220-wip-bl-spi-offload-ad7380-v1-1-838aa873e62a@baylibre.com>
On 2/20/25 12:03 PM, Angelo Dureghello wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Add support for SPI offload to the ad7380 driver. SPI offload allows
> sampling data at the max sample rate (2MSPS with one SDO line).
>
> This is developed and tested against the ADI example FPGA design for
> this family of ADCs [1].
>
> [1]: http://analogdevicesinc.github.io/hdl/projects/ad738x_fmc/index.html
>
> Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
> ---
We forgot to also update Documentation/iio/ad7380.rst. We can follow up
with a separate patch later though.
> drivers/iio/adc/Kconfig | 2 +
> drivers/iio/adc/ad7380.c | 509 +++++++++++++++++++++++++++++++++++++++++++----
> 2 files changed, 475 insertions(+), 36 deletions(-)
>
...
> #define _AD7380_CHANNEL(index, bits, diff, sign, gain) { \
> .type = IIO_VOLTAGE, \
> .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | \
> @@ -237,48 +335,123 @@ static const struct iio_scan_type ad7380_scan_type_16_u[] = {
> .num_event_specs = ARRAY_SIZE(ad7380_events), \
> }
>
> +#define _AD7380_OFFLOAD_CHANNEL(index, bits, diff, sign, gain) { \
> + .type = IIO_VOLTAGE, \
> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | \
> + ((gain) ? BIT(IIO_CHAN_INFO_SCALE) : 0) | \
> + ((diff) ? 0 : BIT(IIO_CHAN_INFO_OFFSET)), \
> + .info_mask_shared_by_type = ((gain) ? 0 : BIT(IIO_CHAN_INFO_SCALE)) | \
> + BIT(IIO_CHAN_INFO_OVERSAMPLING_RATIO) | \
> + BIT(IIO_CHAN_INFO_SAMP_FREQ), \
Not sure if this is worth troubling with, but it might make more sense to make
IIO_CHAN_INFO_SAMP_FREQ info_mask_separate instead of info_mask_shared_by_type,
at least in the case of the single-ended chips.
This family of chips does simultaneous conversions so shared_by_type (or shared_by_all)
would typically be the right thing to do here. However, the single-ended versions
of these chips also have a multiplexer, so there are 2 banks of simultaneously
sampled inputs. So the effective sample rate as far as IIO is concerned would
actually be 1/2 of the sampling_frequency attribute value.
Since we have a channel mask restriction where we force all channels in a bank
to be enabled at once, I think it would work to make IIO_CHAN_INFO_SAMP_FREQ
info_mask_separate where the reported sampling frequency is the conversion rate
divided by the number of channels in a bank.
> + .info_mask_shared_by_type_available = \
> + BIT(IIO_CHAN_INFO_OVERSAMPLING_RATIO) | \
> + BIT(IIO_CHAN_INFO_SAMP_FREQ), \
> + .indexed = 1, \
> + .differential = (diff), \
> + .channel = (diff) ? (2 * (index)) : (index), \
> + .channel2 = (diff) ? (2 * (index) + 1) : 0, \
> + .scan_index = (index), \
> + .has_ext_scan_type = 1, \
> + .ext_scan_type = ad7380_scan_type_##bits##_##sign##_offload, \
> + .num_ext_scan_type = \
> + ARRAY_SIZE(ad7380_scan_type_##bits##_##sign##_offload), \
> + .event_spec = ad7380_events, \
> + .num_event_specs = ARRAY_SIZE(ad7380_events), \
> +}
> +
next prev parent reply other threads:[~2025-02-22 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 18:03 [PATCH] iio: ad7380: add support for SPI offload Angelo Dureghello
2025-02-22 16:31 ` Jonathan Cameron
2025-02-22 17:31 ` David Lechner [this message]
2025-02-25 9:48 ` Angelo Dureghello
2025-03-14 20:03 ` David Lechner
2025-03-15 18:15 ` 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=7b64c6a9-0606-45ba-be45-7ae11c4fdf39@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=adureghello@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox