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>,
	"David Lechner" <dlechner@baylibre.com>,
	"Eddie James" <eajames@linux.ibm.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Jonathan Cameron" <jonathan.cameron@oss.qualcomm.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sashiko <sashiko-bot@kernel.org>,
	"Arnav Kapoor" <kapoorarnav43@gmail.com>
Subject: Re: [PATCH v2] iio: pressure: dps310: don't wait for new temperature in trigger handler
Date: Sat, 14 Nov 2026 01:38:17 +0000	[thread overview]
Message-ID: <20261114013817.476f8fb9@jic23-hlaptop> (raw)
In-Reply-To: <20261113230241.82046-1-zoone.rupert@gmail.com>

On Sat, 14 Nov 2026 01:02:41 +0200
Rupesh Majhi <zoone.rupert@gmail.com> wrote:

> Each scan waits for a new temperature result before reading pressure.
> With pressure sampled faster than temperature, scans then come at the
> temperature rate: an 8 Hz trigger with temperature at its default 1 Hz
> gives one scan a second.
> 
> Read pressure first and take the latest temperature, as a direct
> pressure read already does. Wait for temperature only when pressure is
> not in the scan. Read a temperature in probe, so there is a latest one
> from the first scan on.

That was potentially a while back.  Why not do it in preenable for the buffer?
Will make the buffer start a bit slow but should 'work' from there on.

> 
> Fixes: 9b7cad9ce2ed ("iio: pressure: dps310: add triggered buffer support")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20261110154254.39092-1-zoone.rupert%40gmail.com
> Signed-off-by: Rupesh Majhi <zoone.rupert@gmail.com>
> ---
> v2: read a temperature in probe, so the first scans have one (Arnav Kapoor)
> v1: https://lore.kernel.org/linux-iio/20261111195118.36853-1-zoone.rupert@gmail.com/
> 
> Cc: Arnav Kapoor <kapoorarnav43@gmail.com>
> Cc: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
> 
>  drivers/iio/pressure/dps310.c | 26 ++++++++++++++++++--------
>  1 file changed, 18 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/iio/pressure/dps310.c b/drivers/iio/pressure/dps310.c
> index 85df58ac1809..3d05540f95dd 100644
> --- a/drivers/iio/pressure/dps310.c
> +++ b/drivers/iio/pressure/dps310.c
> @@ -910,10 +910,18 @@ static int dps310_fill_channels(struct dps310_data *data,
>  	unsigned int i;
>  	int rc;
>  
> -	/* Compensation needs a temperature, so it is sampled either way */
> -	rc = dps310_read_temp_raw_locked(data);
> -	if (rc)
> -		return rc;
> +	if (test_bit(DPS310_SCAN_PRESSURE, scan_mask)) {
> +		rc = dps310_read_pres_raw_locked(data);
> +		if (rc)
> +			return rc;
> +
> +		/* Waiting here would hold scans to the temperature rate */
> +		dps310_refresh_temp_locked(data);
> +	} else {
> +		rc = dps310_read_temp_raw_locked(data);
> +		if (rc)
> +			return rc;
> +	}
>  
>  	i = 0;
>  	if (test_bit(DPS310_SCAN_TEMP, scan_mask)) {
> @@ -924,10 +932,6 @@ static int dps310_fill_channels(struct dps310_data *data,
>  	}
>  
>  	if (test_bit(DPS310_SCAN_PRESSURE, scan_mask)) {
> -		rc = dps310_read_pres_raw_locked(data);
> -		if (rc)
> -			return rc;
> -
>  		/* Pascals, see the channel definition */
>  		rc = dps310_calculate_pressure(data, &channels[i++]);
>  		if (rc)
> @@ -1017,6 +1021,12 @@ static int dps310_probe(struct i2c_client *client)
>  	if (rc)
>  		return rc;
>  
> +	/* Pressure compensation needs a temperature from the start */
> +	scoped_guard(mutex, &data->lock)
> +		rc = dps310_read_temp_raw_locked(data);
> +	if (rc)
> +		return rc;
> +
>  	/*
>  	 * The device measures continuously in background mode, so a capture is
>  	 * just a read of the latest results. The trigger is not aligned with
> 
> base-commit: 9752760146e642f3e4a2ec860f8767fa72030d2c


      reply	other threads:[~2026-11-14  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 23:02 Rupesh Majhi
2026-11-14  1:38 ` Jonathan Cameron [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=20261114013817.476f8fb9@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eajames@linux.ibm.com \
    --cc=jonathan.cameron@oss.qualcomm.com \
    --cc=kapoorarnav43@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sashiko-bot@kernel.org \
    --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®