From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Liu Yufei <lyf98405@gmail.com>
Cc: "Alex Lanzano" <lanzano.alex@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Gustavo Silva" <gustavograzs@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: imu: bmi270: fix zero timestamp in triggered buffer
Date: Thu, 29 Oct 2026 15:19:05 +0200 [thread overview]
Message-ID: <auNHyQGAcTcq8G2V@ashevche-desk.local> (raw)
In-Reply-To: <auID4_vQSZXuNk0Q@gmail.com>
On Wed, Oct 28, 2026 at 10:24:11PM +0800, Liu Yufei wrote:
> On Wed, Oct 28, 2026 at 10:58:25AM +0200, Andy Shevchenko wrote:
> > On Wed, Oct 28, 2026 at 10:59:26AM +0800, Liu Yufei wrote:
...
> > > + s64 timestamp = iio_get_time_ns(indio_dev);
> >
> > Do we need this variable? Why not call it directly?
>
> The intent was to capture the timestamp before the bus read, so it is
> as close as possible to the data ready event rather than after the
> regmap_bulk_read() over I2C/SPI.
>
> If that difference is not considered significant here, I'm happy to
> call it directly in v2.
But the time of the event in the kernel should be ideally with data we get,
not in the past, right?
Jonathan, what our expectations / requirements on the timestamp capture?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-29 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 2:59 Liu Yufei
2026-10-28 8:58 ` Andy Shevchenko
2026-10-28 14:24 ` Liu Yufei
2026-10-29 13:19 ` Andy Shevchenko [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=auNHyQGAcTcq8G2V@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gustavograzs@gmail.com \
--cc=jic23@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyf98405@gmail.com \
--cc=nuno.sa@analog.com \
--cc=stable@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
all inboxes | Powered by JetHome®