From: Md Shofiqul Islam <shofiqtest@gmail.com>
To: jic23@kernel.org
Cc: andy@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
dlechner@baylibre.com, nuno.sa@analog.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] iio: accel: adxl3xx: Add timestamps to FIFO data
Date: Thu, 14 May 2026 21:35:37 +0300 [thread overview]
Message-ID: <177878373700.35036.18408837738235928455@gmail.com> (raw)
In-Reply-To: <20260510082556.3867-1-shofiqtest@gmail.com>
On Mon, 11 May 2026, Jonathan Cameron wrote:
> It is possible to approximate the correct timestamps but it's complex.
> You definitely don't want to try getting timestamps working for a fifo
> equipped part without real hardware so you can plot them over time and
> verify there are no inconsistencies or bugs in your timestamp
> approximation algorithm.
Understood -- thank you for the detailed explanation. I'll drop this
series. I don't have access to any of the ADXL hardware so I cannot
validate a per-sample timestamp approximation algorithm. I'll leave
this for someone with real devices to pick up when they are ready to
implement it properly, with the correct per-sample backfilling from
the FIFO watermark timestamp.
Thanks,
Shofiq
prev parent reply other threads:[~2026-05-14 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 8:25 [PATCH 0/5] iio: accel: adxl3xx: Add timestamps to FIFO data Md Shofiqul Islam
2026-05-10 8:25 ` [PATCH 1/5] iio: accel: adxl372: Add timestamp " Md Shofiqul Islam
2026-05-16 18:55 ` David Lechner
2026-05-17 11:30 ` Jonathan Cameron
2026-05-17 12:48 ` Md Shofiqul Islam
2026-05-10 8:25 ` [PATCH 2/5] iio: accel: adxl380: " Md Shofiqul Islam
2026-05-10 8:25 ` [PATCH 3/5] iio: accel: adxl367: " Md Shofiqul Islam
2026-05-10 8:25 ` [PATCH 4/5] iio: accel: adxl313: " Md Shofiqul Islam
2026-05-10 8:25 ` [PATCH 5/5] iio: accel: adxl345: " Md Shofiqul Islam
2026-05-10 12:58 ` [PATCH 0/5] iio: accel: adxl3xx: Add timestamps " Andy Shevchenko
[not found] ` <CAOTCDVsUF1qaYgSGa4hcDYOqmMpkK2G+HYeQ=ShQ1oEbM8nGJQ@mail.gmail.com>
2026-05-11 14:41 ` Jonathan Cameron
2026-05-14 18:35 ` Md Shofiqul Islam [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=177878373700.35036.18408837738235928455@gmail.com \
--to=shofiqtest@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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