From: Rupesh Majhi <zoone.rupert@gmail.com>
To: jic23@kernel.org
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Bill Wendling" <morbo@google.com>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Joel Stanley" <joel@jms.id.au>,
"Justin Stitt" <justinstitt@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v6 5/6] iio: pressure: dps310: add hardware FIFO support
Date: Thu, 17 Sep 2026 00:02:23 +0300 [thread overview]
Message-ID: <20260916210223.15456-1-zoone.rupert@gmail.com> (raw)
In-Reply-To: <20260910033636.3a2ed151@jic23-hlaptop>
On Thu, 10 Sep 2026 03:36:36 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> Maybe we just set the minimum allowed watermark to something that
> in practice always has a temperature (or almost does)? It's kind
> of true that a watermark below that doesn't work because we end
> up dropping data.
Two temperature entries are prs_rate / tmp_rate pressure entries apart, so
a batch needs one more than that before it is sure of catching one. The
FIFO holds 32, so there is no such watermark once the ratio reaches 32.
That is six of the 64 rate pairs, and one of them is pressure 32 Hz with
temperature 1 Hz, the case that found this, which would want 33.
So I will hold them locally instead, which is what you asked for first. The
drain timer runs at half the fill time, so nothing overflows while the
driver waits, and the hold lasts only until the first temperature of the
session, bounded by the rate ratio at 128 entries. The first push still
waits for that temperature, but only once per enable, and no pressure entry
is dropped. I will re-run the zero output regression against it.
> Validity flag in the data we push to userspace? That never works because
> we don't have a universal encoding for one.
I meant driver state, not a channel. Moot now.
Rupesh
next prev parent reply other threads:[~2026-09-16 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 20:11 [PATCH v6 0/6] iio: pressure: dps310: FIFO and triggered buffer support Rupesh Majhi
2026-08-24 20:11 ` [PATCH v6 1/6] iio: pressure: dps310: fix CFG_REG bit definitions Rupesh Majhi
2026-08-24 20:11 ` [PATCH v6 2/6] iio: pressure: dps310: use a local device pointer in probe Rupesh Majhi
2026-08-24 20:12 ` [PATCH v6 3/6] iio: pressure: dps310: rework the raw read paths Rupesh Majhi
2026-08-25 8:59 ` Andy Shevchenko
2026-08-24 20:12 ` [PATCH v6 4/6] iio: pressure: dps310: add triggered buffer support Rupesh Majhi
2026-08-25 9:06 ` Andy Shevchenko
2026-08-31 0:41 ` Jonathan Cameron
2026-08-31 7:03 ` Andy Shevchenko
2026-09-06 10:06 ` Rupesh Majhi
2026-08-31 1:14 ` Jonathan Cameron
2026-08-24 20:12 ` [PATCH v6 5/6] iio: pressure: dps310: add hardware FIFO support Rupesh Majhi
2026-08-25 9:39 ` Andy Shevchenko
2026-09-06 10:07 ` Rupesh Majhi
2026-08-31 1:14 ` Jonathan Cameron
2026-09-06 9:45 ` Rupesh Majhi
2026-09-10 2:36 ` Jonathan Cameron
2026-09-16 21:02 ` Rupesh Majhi [this message]
2026-09-17 2:34 ` Jonathan Cameron
2026-08-24 20:12 ` [PATCH v6 6/6] iio: pressure: dps310: check the lock markings with context analysis Rupesh Majhi
2026-08-31 1:14 ` Jonathan Cameron
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=20260916210223.15456-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=joel@jms.id.au \
--cc=justinstitt@google.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--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®