From: Md Shofiqul Islam <shofiqtest@gmail.com>
To: dlechner@baylibre.com
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio: accel: adxl372: Add timestamp to FIFO data
Date: Sun, 17 May 2026 02:19:24 -0700 (PDT) [thread overview]
Message-ID: <6a09881c.7a23d47e.35947f.2f62@mx.google.com> (raw)
In-Reply-To: <20260516211935.36773-1-shofiqtest@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Hi David,
Thank you for the two review comments.
Regarding the timestamp accuracy concern from the v1 discussion: the commit
message in v3 now explicitly documents this. The timestamp is captured once
per FIFO watermark interrupt and reused for all samples drained in that
invocation. It is most accurate for the last sample in the burst and
progressively stale for earlier ones. This is noted as an acceptable
approximation for coarse event sequencing, consistent with watermark-based
FIFO readout in other IIO accelerometer drivers.
Regarding the function choice: Stepan Ionichev identified that
iio_push_to_buffers_with_ts() writes the timestamp directly into the source
buffer during the loop, corrupting subsequent FIFO entries. v3 switches to
iio_push_to_buffers_with_ts_unaligned() which copies into an internal bounce
buffer without modifying the caller's data. The size argument remains
st->fifo_set_size * sizeof(__be16) -- the actual per-sample data length --
which _unaligned() caps at min(scan_bytes, data_sz) internally.
v3 is at:
[PATCH v3] iio: accel: adxl372: Add timestamp to FIFO data
Message-ID: <20260517091735.135610-1-shofiqtest@gmail.com>
Md Shofiqul Islam
next prev parent reply other threads:[~2026-05-17 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 21:19 [PATCH v2] iio: accel: adxl372: Add timestamp to FIFO data Md Shofiqul Islam
2026-05-16 23:35 ` David Lechner
2026-05-16 23:36 ` David Lechner
2026-05-17 7:14 ` Stepan Ionichev
2026-05-17 9:17 ` [PATCH v3] " Md Shofiqul Islam
2026-05-17 9:19 ` Md Shofiqul Islam [this message]
2026-05-17 12:57 ` [PATCH v2] " Jonathan Cameron
2026-05-17 9:19 ` Md Shofiqul Islam
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=6a09881c.7a23d47e.35947f.2f62@mx.google.com \
--to=shofiqtest@gmail.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
/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