Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Rupesh Majhi <zoone.rupert@gmail.com>
Cc: eajames@linux.ibm.com, dlechner@baylibre.com, nuno.sa@analog.com,
	andy@kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: pressure: dps310: add FIFO support
Date: Sat, 18 Jul 2026 22:44:55 +0100	[thread overview]
Message-ID: <20260718224455.38acd927@jic23-huawei> (raw)
In-Reply-To: <20260718211727.39752-1-zoone.rupert@gmail.com>

On Sun, 19 Jul 2026 00:17:26 +0300
Rupesh Majhi <zoone.rupert@gmail.com> wrote:

> The DPS310 has a 32-sample FIFO that buffers pressure and temperature
> readings. The FIFO_EN bit was defined but never used.
> 
> This enables the FIFO in the probe after startup. Add the necessary
> register defines and init/flush functions. If FIFO init fails, driver
> falls back to single-shot mode.
> 
> Signed-off-by: Rupesh Majhi <zoone.rupert@gmail.com>
Hi Rupesh,

This looks to be a v2. So check Documentation/process/submitting-patches.rst
for the format and use that if you need a v3.

> ---
Also change log needed here.

I thought you were going to submit v2 with the full buffered support?
Perhaps this was an accidental resend of the earlier code.

Jonathan


  reply	other threads:[~2026-07-18 21:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 21:17 [PATCH] iio: pressure: dps310: add FIFO support Rupesh Majhi
2026-07-18 21:44 ` Jonathan Cameron [this message]
2026-07-18 23:51   ` [PATCH v3] iio: pressure: dps310: add triggered buffer support Rupesh Majhi
2026-07-19  8:47     ` Andy Shevchenko
2026-07-19  8:48       ` Andy Shevchenko
2026-07-19 21:48       ` Jonathan Cameron
2026-07-19 22:11     ` Jonathan Cameron
2026-07-20  5:56       ` Rupert Zoone
2026-07-23 23:42         ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2026-05-18 16:53 [PATCH] iio: pressure: dps310: add FIFO support Rupesh Majhi
2026-05-18 18:58 ` Jonathan Cameron
     [not found]   ` <CABpb+S7rW5c_40eCLesRq8yVeUziQYK9x8Uy-FBJ4z_JqhGPDQ@mail.gmail.com>
2026-05-21 12:25     ` Rupert Zoone

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=20260718224455.38acd927@jic23-huawei \
    --to=jonathan.cameron@oss.qualcomm.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eajames@linux.ibm.com \
    --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