From: David Lechner <dlechner@baylibre.com>
To: David Laight <david.laight.linux@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Eugen Hristev" <eugen.hristev@linaro.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/7] iio: make IIO_DMA_MINALIGN minimum of 8 bytes
Date: Thu, 8 May 2025 16:44:18 -0500 [thread overview]
Message-ID: <43fd5216-9577-4773-86c3-e3035f3934b7@baylibre.com> (raw)
In-Reply-To: <20250508223959.70e909d2@pumpkin>
On 5/8/25 4:39 PM, David Laight wrote:
> On Mon, 05 May 2025 11:31:42 -0500
> David Lechner <dlechner@baylibre.com> wrote:
>
>> Add a condition to ensure that IIO_DMA_MINALIGN is at least 8 bytes.
>> On some 32-bit architectures, IIO_DMA_MINALIGN is 4. In many cases,
>> drivers are using this alignment for buffers that include a 64-bit
>> timestamp that is used with iio_push_to_buffers_with_ts(), which expects
>> the timestamp to be aligned to 8 bytes. To handle this, we can just make
>> IIO_DMA_MINALIGN at least 8 bytes.
>>
>> Signed-off-by: David Lechner <dlechner@baylibre.com>
>> ---
>> include/linux/iio/iio.h | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
>> index 638cf2420fbd85cf2924d09d061df601d1d4bb2a..7e1e3739328d103262071bd34ba5f6631163c122 100644
>> --- a/include/linux/iio/iio.h
>> +++ b/include/linux/iio/iio.h
>> @@ -775,8 +775,18 @@ static inline void *iio_device_get_drvdata(const struct iio_dev *indio_dev)
>> * to in turn include IIO_DMA_MINALIGN'd elements such as buffers which
>> * must not share cachelines with the rest of the structure, thus making
>> * them safe for use with non-coherent DMA.
>> + *
>> + * A number of drivers also use this on buffers that include a 64-bit timestamp
>> + * that is used with iio_push_to_buffer_with_ts(). Therefore, in the case where
>> + * DMA alignment is not sufficient for proper timestamp alignment, we align to
>> + * 8 bytes instead.
>> */
>> +#if ARCH_DMA_MINALIGN < sizeof(s64)
>> +#define IIO_DMA_MINALIGN sizeof(s64)
>> +#else
>> #define IIO_DMA_MINALIGN ARCH_DMA_MINALIGN
>> +#endif
>
> Did you actually test this?
> You can't use sizeof() in a pre-processor conditional.
Pretty sure I did, but maybe I was asleep at the wheel. Anyway, this got caught
by a build bot and I realized the mistake.
>
> David
>
>> +
>> struct iio_dev *iio_device_alloc(struct device *parent, int sizeof_priv);
>>
>> /* The information at the returned address is guaranteed to be cacheline aligned */
>>
>
next prev parent reply other threads:[~2025-05-08 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 16:31 [PATCH v5 0/7] iio: introduce IIO_DECLARE_BUFFER_WITH_TS David Lechner
2025-05-05 16:31 ` [PATCH v5 1/7] iio: make IIO_DMA_MINALIGN minimum of 8 bytes David Lechner
2025-05-07 20:02 ` Jonathan Cameron
2025-05-08 21:39 ` David Laight
2025-05-08 21:44 ` David Lechner [this message]
2025-05-05 16:31 ` [PATCH v5 2/7] iio: introduce IIO_DECLARE_BUFFER_WITH_TS macros David Lechner
2025-05-05 16:31 ` [PATCH v5 3/7] iio: adc: ad4695: use IIO_DECLARE_DMA_BUFFER_WITH_TS David Lechner
2025-05-05 16:31 ` [PATCH v5 4/7] iio: adc: ad4695: rename AD4695_MAX_VIN_CHANNELS David Lechner
2025-05-05 16:31 ` [PATCH v5 5/7] iio: adc: ad7380: use IIO_DECLARE_DMA_BUFFER_WITH_TS David Lechner
2025-05-05 16:31 ` [PATCH v5 6/7] iio: accel: sca3300: use IIO_DECLARE_BUFFER_WITH_TS David Lechner
2025-05-07 6:37 ` Nuno Sá
2025-05-05 16:31 ` [PATCH v5 7/7] iio: adc: at91-sama5d2: " David Lechner
2025-05-05 16:47 ` [PATCH v5 0/7] iio: introduce IIO_DECLARE_BUFFER_WITH_TS Jonathan Cameron
2025-05-07 6:39 ` Nuno Sá
2025-05-07 19:54 ` 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=43fd5216-9577-4773-86c3-e3035f3934b7@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=david.laight.linux@gmail.com \
--cc=eugen.hristev@linaro.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--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
all inboxes | Powered by JetHome®