From: Rupesh Majhi <zoone.rupert@gmail.com>
To: "Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Rupesh Majhi <zoone.rupert@gmail.com>
Subject: [PATCH v9 0/3] iio: pressure: dps310: hardware FIFO support
Date: Tue, 29 Sep 2026 00:11:24 +0300 [thread overview]
Message-ID: <20260928211127.641828-1-zoone.rupert@gmail.com> (raw)
Rest of v8, rebased on iio/testing where 1-6 and 10 now are.
Since v8, both in patch 1:
- a held entry that fails to compensate is dropped. v8 kept it and
retried it at every temperature entry, failing that drain and losing
rest of its batch. With one bad entry injected on hardware, v8 lost
20 to 45% of samples and v9 only that entry
- postenable takes the lock by hand instead of mixing guard() and goto
On your question about out-of-range values in the FIFO: none seen from
real data at any oversampling ratio. Checking turned up an s64 overflow in
pressure compensation, fixed on its own:
https://lore.kernel.org/linux-iio/20260928101803.547005-1-zoone.rupert@gmail.com/
Retested on a DPS310 on a BeagleBone Black: six of six buffer enables
produce data, flush race test clean. Built with clang 23 and
CONFIG_WARN_CONTEXT_ANALYSIS, no warnings.
Clang annotation for the mode claim helpers, from Andy's question on v7
9/10, comes as its own series, with at_least for dps310_fill_channels().
Cleanup series after that.
Rupesh Majhi (3):
iio: pressure: dps310: read buffered samples from the hardware FIFO
iio: pressure: dps310: derive the drain interval from the watermark
iio: pressure: dps310: implement .hwfifo_flush_to_buffer()
drivers/iio/pressure/dps310.c | 410 +++++++++++++++++++++++++++++++++-
1 file changed, 400 insertions(+), 10 deletions(-)
base-commit: a3b3580713f3ac5a32dc2874ee546828977a1d68
--
2.43.0
next reply other threads:[~2026-09-28 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 21:11 Rupesh Majhi [this message]
2026-09-28 21:11 ` [PATCH v9 1/3] iio: pressure: dps310: read buffered samples from the hardware FIFO Rupesh Majhi
2026-09-28 21:55 ` Andy Shevchenko
2026-09-28 21:11 ` [PATCH v9 2/3] iio: pressure: dps310: derive the drain interval from the watermark Rupesh Majhi
2026-09-28 21:11 ` [PATCH v9 3/3] iio: pressure: dps310: implement .hwfifo_flush_to_buffer() Rupesh Majhi
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=20260928211127.641828-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=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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®