From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7606: explicit timestamp alignment
Date: Sun, 4 May 2025 15:55:44 +0100 [thread overview]
Message-ID: <20250504155544.60fe3464@jic23-huawei> (raw)
In-Reply-To: <d7f00a8c9d4da6f780c1ec067be2702fa0e60ea1.camel@gmail.com>
On Tue, 29 Apr 2025 14:01:54 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:
> On Mon, 2025-04-28 at 21:17 -0500, David Lechner wrote:
> > Use struct with aligned_s64 timestamp to make timestamp alignment
> > explicit. Technically, what we have works because for all known
> > architectures, IIO_DMA_MINALIGN is a multiple of __alignof__(s64).
> > But this way, we don't have to make people read the comments to know
> > why there are extra elements in each buffer.
> >
> > ---
>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
Applied to the togreg branch of iio.git and pushed out as testing
for all the normal reasons.
Thanks,
Jonathan
>
> > drivers/iio/adc/ad7606.h | 13 ++++++++-----
> > 1 file changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/iio/adc/ad7606.h b/drivers/iio/adc/ad7606.h
> > index
> > 89d49551eaf515bab9706c12bff056dfcb707b67..441e62c521bcbea69b4f70bb2d55f65334d2
> > 2276 100644
> > --- a/drivers/iio/adc/ad7606.h
> > +++ b/drivers/iio/adc/ad7606.h
> > @@ -155,12 +155,15 @@ struct ad7606_state {
> > /*
> > * DMA (thus cache coherency maintenance) may require the
> > * transfer buffers to live in their own cache lines.
> > - * 16 * 16-bit samples + 64-bit timestamp - for AD7616
> > - * 8 * 32-bit samples + 64-bit timestamp - for AD7616C-18 (and
> > similar)
> > + * 16 * 16-bit samples for AD7616
> > + * 8 * 32-bit samples for AD7616C-18 (and similar)
> > */
> > - union {
> > - u16 buf16[20];
> > - u32 buf32[10];
> > + struct {
> > + union {
> > + u16 buf16[16];
> > + u32 buf32[8];
> > + };
> > + aligned_s64 timestamp;
> > } data __aligned(IIO_DMA_MINALIGN);
> > __be16 d16[2];
> > };
> >
> > ---
> > base-commit: b475195fecc79a1a6e7fb0846aaaab0a1a4cb2e6
> > change-id: 20250428-iio-adc-ad7606-fix-buffer-alignment-9fcde71687dc
> >
> > Best regards,
next prev parent reply other threads:[~2025-05-04 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:17 [PATCH] iio: adc: ad7606: explicit timestamp alignment David Lechner
2025-04-29 13:01 ` Nuno Sá
2025-05-04 14:55 ` Jonathan Cameron [this message]
2025-05-05 13:57 ` David Lechner
2025-05-05 15:14 ` 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=20250504155544.60fe3464@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.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