Linux IIO development
 help / color / mirror / Atom feed
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>,
	Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [PATCH v2] iio: commom: st_sensors: ensure proper DMA alignment
Date: Sun, 4 Feb 2024 15:01:35 +0000	[thread overview]
Message-ID: <20240204150135.0fa5a808@jic23-huawei> (raw)
In-Reply-To: <20240131-dev_dma_safety_stm-v2-1-580c07fae51b@analog.com>

On Wed, 31 Jan 2024 10:16:47 +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 st_sensors common buffer.
> 
> While at it, moved the odr_lock before buffer_data as we definitely
> don't want any other data to share a cacheline with the buffer.
> 
> [1]: https://lore.kernel.org/linux-iio/20220508175712.647246-2-jic23@kernel.org/
> 
> Fixes: e031d5f558f1 ("iio:st_sensors: remove buffer allocation at each buffer enable")
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
Applied to the fixes-togreg branch of iio.git and marked for stable. Thanks!

Jonathan

> ---
> Changes in v2:
>  * moved struct odr_lock before buffer_data.
> ---
>  include/linux/iio/common/st_sensors.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/iio/common/st_sensors.h b/include/linux/iio/common/st_sensors.h
> index 607c3a89a647..f9ae5cdd884f 100644
> --- a/include/linux/iio/common/st_sensors.h
> +++ b/include/linux/iio/common/st_sensors.h
> @@ -258,9 +258,9 @@ struct st_sensor_data {
>  	bool hw_irq_trigger;
>  	s64 hw_timestamp;
>  
> -	char buffer_data[ST_SENSORS_MAX_BUFFER_SIZE] ____cacheline_aligned;
> -
>  	struct mutex odr_lock;
> +
> +	char buffer_data[ST_SENSORS_MAX_BUFFER_SIZE] __aligned(IIO_DMA_MINALIGN);
>  };
>  
>  #ifdef CONFIG_IIO_BUFFER
> 
> ---
> base-commit: 1380d453434e276355458e712c743dd071ca1fa7
> change-id: 20240131-dev_dma_safety_stm-7c09782d87ed
> --
> 
> Thanks!
> - Nuno Sá
> 


      reply	other threads:[~2024-02-04 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  9:16 [PATCH v2] iio: commom: st_sensors: ensure proper DMA alignment Nuno Sa
2024-02-04 15:01 ` Jonathan Cameron [this message]

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=20240204150135.0fa5a808@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=denis.ciocca@st.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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