mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rupesh Majhi <zoone.rupert@gmail.com>
Cc: "Andy Shevchenko" <andy@kernel.org>,
	"Bill Wendling" <morbo@google.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Eddie James" <eajames@linux.ibm.com>,
	"Justin Stitt" <justinstitt@google.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH v12 0/5] iio: pressure: dps310: hardware FIFO support
Date: Sun, 11 Oct 2026 15:00:53 +0100	[thread overview]
Message-ID: <20261011145914.05d1c7a6@jic23-hlaptop> (raw)
In-Reply-To: <20261003195012.92948-1-zoone.rupert@gmail.com>

On Sat,  3 Oct 2026 22:50:06 +0300
Rupesh Majhi <zoone.rupert@gmail.com> wrote:

> Rest of FIFO series, on iio/togreg which has 1-6 and 10 of v8.
> 
> Since v11:
>  - patch 1: blank line, Reviewed-by Andy
>  - patch 2: guard() in postenable, setup moved to a helper that kfree()s
>    on error, scoped_guard() in fifo_work, loop counters in the for,
>    ternary on one line, two comments trimmed. The first loop in
>    fifo_drain keeps cnt outside, it is used after the loop.
>  - patch 3: signature wrapped
>  - patch 4: drain comment and commit message trimmed
>  - patch 5: Suggested-by Andy back, assert in the new helper too, still
>    optional
> 
> Pressure overflow fix is now at v4:
> https://lore.kernel.org/linux-iio/20261003185716.32732-1-zoone.rupert@gmail.com/
> Patches 1 and 5 conflict trivially with it. I can rebase on whichever
> goes in first.
> 
> Retested on DPS310 with BeagleBone Black. Lockdep run under QEMU.
> 
> v11: https://lore.kernel.org/linux-iio/20261002072526.250081-1-zoone.rupert@gmail.com/
> 
Applied patches 1-4.   Not this was messy so there was some hand applying needed.
Please check I didn't mess it up!
Maybe we'll still get some more review on these (which is fine as I'm fine tweaking
or dropping them until I rebase on rc1 in a few weeks time). 

However, too much in flight and I wanted to trim down what I was paying attention
to!

I replied with my view on patch 5 in the earlier thread (just now), but definitely
open to hearing more opinions on how far we want to go with annotations.

Thanks,

Jonathan

> Rupesh Majhi (5):
>   iio: pressure: dps310: use devm_mutex_init()
>   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()
>   iio: pressure: dps310: assert the lock at runtime too
> 
>  drivers/iio/pressure/dps310.c | 441 +++++++++++++++++++++++++++++++++-
>  1 file changed, 430 insertions(+), 11 deletions(-)
> 
> 
> base-commit: a3b3580713f3ac5a32dc2874ee546828977a1d68


  parent reply	other threads:[~2026-10-11 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 19:50 Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 1/5] iio: pressure: dps310: use devm_mutex_init() Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 2/5] iio: pressure: dps310: read buffered samples from the hardware FIFO Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 3/5] iio: pressure: dps310: derive the drain interval from the watermark Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 4/5] iio: pressure: dps310: implement .hwfifo_flush_to_buffer() Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 5/5] iio: pressure: dps310: assert the lock at runtime too Rupesh Majhi
2026-10-11 14:00 ` Jonathan Cameron [this message]
2026-10-18 21:24   ` [PATCH v12 0/5] iio: pressure: dps310: hardware FIFO support 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=20261011145914.05d1c7a6@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eajames@linux.ibm.com \
    --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=ndesaulniers@google.com \
    --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®