From: Jonathan Cameron <jic23@kernel.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: "Roan van Dijk" <roan@protonic.nl>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: chemical: scd4x: expose timestamp channel
Date: Sun, 21 Dec 2025 18:05:08 +0000 [thread overview]
Message-ID: <20251221180508.252bd6d9@jic23-huawei> (raw)
In-Reply-To: <20251218151205.1301792-1-fiona.klute@gmx.de>
On Thu, 18 Dec 2025 16:12:05 +0100
Fiona Klute <fiona.klute@gmx.de> wrote:
> Timestamps were already written to the buffer in
> scd4x_trigger_handler(), this patch makes them available as a channel.
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Applied to the togreg branch of iio.git. Initially pushed out as testing
to let 0-day have a brief look at it.
Thanks,
Jonathan
> ---
> drivers/iio/chemical/scd4x.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/chemical/scd4x.c b/drivers/iio/chemical/scd4x.c
> index 0fd839176e264..23a326fb62a7e 100644
> --- a/drivers/iio/chemical/scd4x.c
> +++ b/drivers/iio/chemical/scd4x.c
> @@ -59,6 +59,8 @@ enum scd4x_channel_idx {
> SCD4X_CO2,
> SCD4X_TEMP,
> SCD4X_HR,
> + /* kernel timestamp, at the end of buffer */
> + SCD4X_TS,
> };
>
> struct scd4x_state {
> @@ -615,6 +617,7 @@ static const struct iio_chan_spec scd4x_channels[] = {
> .endianness = IIO_CPU,
> },
> },
> + IIO_CHAN_SOFT_TIMESTAMP(SCD4X_TS),
> };
>
> static int scd4x_suspend(struct device *dev)
next prev parent reply other threads:[~2025-12-21 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 15:12 [PATCH] iio: chemical: scd4x: expose timestamp channel Fiona Klute
2025-12-21 18:05 ` Jonathan Cameron [this message]
2025-12-22 16:39 ` Fiona Klute
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=20251221180508.252bd6d9@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=fiona.klute@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=roan@protonic.nl \
/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