From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: Rupesh Majhi <zoone.rupert@gmail.com>
Cc: "Paulius Zaleckas" <paulius.zaleckas@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Joel Stanley" <joel@jms.id.au>, "Nuno Sá" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: pressure: dps310: fix input checks and resets
Date: Wed, 4 Nov 2026 11:13:50 +0200 [thread overview]
Message-ID: <20261104091351.710582-1-paulius.zaleckas@gmail.com> (raw)
In-Reply-To: <20261103223008.12675-1-zoone.rupert@gmail.com>
On Tue, Nov 03, 2026, Rupesh Majhi wrote:
> Jonathan is holding this series for your Tested-by. Could you give it a
> run on the ZTS8032 when you have time?
Tested on a ZTS8032, on iio testing backported to 6.12:
- 0 and 0.5 are rejected for both rates and ratios.
- 64x at 4 Hz survives a timeout reset forced by putting the chip in
standby behind the driver's back.
- A warm reboot during a FIFO capture: FIFO_EN is clear after probe
and reads work.
Tested-by: Paulius Zaleckas <paulius.zaleckas@gmail.com>
Paulius
prev parent reply other threads:[~2026-11-04 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 22:06 Rupesh Majhi
2026-10-29 22:06 ` [PATCH 1/3] iio: pressure: dps310: reject a zero rate or oversampling ratio Rupesh Majhi
2026-10-30 8:17 ` Joshua Crofts
2026-10-29 22:06 ` [PATCH 2/3] iio: pressure: dps310: reset the chip at probe Rupesh Majhi
2026-10-30 8:19 ` Joshua Crofts
2026-11-01 1:03 ` Jonathan Cameron
2026-11-01 1:04 ` Jonathan Cameron
2026-11-01 10:58 ` Rupesh Majhi
2026-11-01 17:30 ` Jonathan Cameron
2026-10-29 22:06 ` [PATCH 3/3] iio: pressure: dps310: keep the user's settings across a timeout reset Rupesh Majhi
2026-10-30 8:22 ` Joshua Crofts
2026-11-03 22:30 ` [PATCH 0/3] iio: pressure: dps310: fix input checks and resets Rupesh Majhi
2026-11-04 9:13 ` Paulius Zaleckas [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=20261104091351.710582-1-paulius.zaleckas@gmail.com \
--to=paulius.zaleckas@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=jic23@kernel.org \
--cc=joel@jms.id.au \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=zoone.rupert@gmail.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
all inboxes | Powered by JetHome®