From: Rupesh Majhi <zoone.rupert@gmail.com>
To: jic23@kernel.org
Cc: "Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Cameron" <jonathan.cameron@oss.qualcomm.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Sashiko <sashiko-bot@kernel.org>,
"Arnav Kapoor" <kapoorarnav43@gmail.com>
Subject: Re: [PATCH v2] iio: pressure: dps310: don't wait for new temperature in trigger handler
Date: Sat, 14 Nov 2026 10:35:25 +0200 [thread overview]
Message-ID: <20261114083525.11972-1-zoone.rupert@gmail.com> (raw)
In-Reply-To: <20261114013817.476f8fb9@jic23-hlaptop>
On Sat, 14 Nov 2026 01:38:17 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> > Read pressure first and take the latest temperature, as a direct
> > pressure read already does. Wait for temperature only when pressure is
> > not in the scan. Read a temperature in probe, so there is a latest one
> > from the first scan on.
>
> That was potentially a while back. Why not do it in preenable for the buffer?
> Will make the buffer start a bit slow but should 'work' from there on.
Probe value only lasts until the next temperature result. By the
time the buffer starts TMP_RDY is set, so first scan takes a new
temperature anyway (checked on the board, buffer enabled 5 s after
probe). The probe read also covers direct pressure reads.
Happy to move it to preenable if you prefer.
Thanks,
Rupesh
prev parent reply other threads:[~2026-11-14 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:02 Rupesh Majhi
2026-11-14 1:38 ` Jonathan Cameron
2026-11-14 8:35 ` Rupesh Majhi [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=20261114083525.11972-1-zoone.rupert@gmail.com \
--to=zoone.rupert@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kapoorarnav43@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sashiko-bot@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®