From: Rupesh Majhi <zoone.rupert@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>, "Rob Herring" <robh@kernel.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Paulius Zaleckas" <paulius.zaleckas@gmail.com>
Subject: Re: [PATCH v2 2/2] iio: pressure: dps310: add a data-ready trigger
Date: Sat, 14 Nov 2026 13:58:01 +0200 [thread overview]
Message-ID: <20261114115801.57701-1-zoone.rupert@gmail.com> (raw)
In-Reply-To: <sashiko-outbox-214316@kernel.org>
On Sat, 14 Nov 2026 08:59:52 +0000
sashiko-bot@kernel.org wrote:
> Does triggering on DPS310_INT_PRS block in dps310_fill_channels() waiting
> for DPS310_TMP_RDY whenever the pressure rate exceeds the temperature rate?
Yes, without the trigger handler fix the cover letter points to:
https://lore.kernel.org/linux-iio/20261113230241.82046-1-zoone.rupert@gmail.com/
It is against the fixes branch, so this base does not have it. With it
applied the handler does not wait: 32 scans in 4 s with pressure at
8 Hz and temperature at 1 Hz, 5 without.
Rupesh
prev parent reply other threads:[~2026-11-14 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 8:38 [PATCH v2 0/2] iio: pressure: dps310: data-ready trigger Rupesh Majhi
2026-11-14 8:38 ` [PATCH v2 1/2] dt-bindings: iio: pressure: infineon,dps310: Add interrupts Rupesh Majhi
2026-11-14 8:38 ` [PATCH v2 2/2] iio: pressure: dps310: add a data-ready trigger Rupesh Majhi
2026-11-14 8:59 ` sashiko-bot
2026-11-14 11:58 ` 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=20261114115801.57701-1-zoone.rupert@gmail.com \
--to=zoone.rupert@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=paulius.zaleckas@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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