From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>, Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
"Renato Lui Geh" <renatogeh@gmail.com>,
Fabrizio Lamarque <fl.scratchpad@gmail.com>
Subject: Re: [PATCH 1/2] iio: adc: ad_sigma_delta: ensure proper DMA alignment
Date: Sun, 21 Jan 2024 16:19:34 +0000 [thread overview]
Message-ID: <20240121161934.4d71ebab@jic23-huawei> (raw)
In-Reply-To: <20240117-dev_sigma_delta_no_irq_flags-v1-1-db39261592cf@analog.com>
On Wed, 17 Jan 2024 13:41:03 +0100
Nuno Sa <nuno.sa@analog.com> wrote:
> Aligning the buffer to the L1 cache is not sufficient in some platforms
> as they might have larger cacheline sizes for caches after L1 and thus,
> we can't guarantee DMA safety.
>
> That was the whole reason to introduce IIO_DMA_MINALIGN in [1]. Do the same
> for the sigma_delta ADCs.
>
> [1]: https://lore.kernel.org/linux-iio/20220508175712.647246-2-jic23@kernel.org/
> Fixes: 0fb6ee8d0b5e ("iio: ad_sigma_delta: Don't put SPI transfer buffer on the stack")
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
> ---
> include/linux/iio/adc/ad_sigma_delta.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/iio/adc/ad_sigma_delta.h b/include/linux/iio/adc/ad_sigma_delta.h
> index 7852f6c9a714..719cf9cc6e1a 100644
> --- a/include/linux/iio/adc/ad_sigma_delta.h
> +++ b/include/linux/iio/adc/ad_sigma_delta.h
> @@ -8,6 +8,8 @@
> #ifndef __AD_SIGMA_DELTA_H__
> #define __AD_SIGMA_DELTA_H__
>
> +#include <linux/iio/iio.h>
> +
> enum ad_sigma_delta_mode {
> AD_SD_MODE_CONTINUOUS = 0,
> AD_SD_MODE_SINGLE = 1,
> @@ -99,7 +101,7 @@ struct ad_sigma_delta {
> * 'rx_buf' is up to 32 bits per sample + 64 bit timestamp,
> * rounded to 16 bytes to take into account padding.
> */
> - uint8_t tx_buf[4] ____cacheline_aligned;
> + uint8_t tx_buf[4] __aligned(IIO_DMA_MINALIGN);
> uint8_t rx_buf[16] __aligned(8);
> };
>
>
next prev parent reply other threads:[~2024-01-21 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:41 [PATCH 0/2] iio: adc: ad_sigma_delta: misc fixes/improvements Nuno Sa
2024-01-17 12:41 ` [PATCH 1/2] iio: adc: ad_sigma_delta: ensure proper DMA alignment Nuno Sa
2024-01-21 16:19 ` Jonathan Cameron [this message]
2024-01-17 12:41 ` [PATCH 2/2] iio: adc: ad_sigma_delta: allow overwriting the IRQ flags Nuno Sa
2024-01-21 16:22 ` 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=20240121161934.4d71ebab@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=fl.scratchpad@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=renatogeh@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