public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: inv.git-commit@tdk.com
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
	stable@vger.kernel.org,
	Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH] iio: invensense: fix odr switching to same value
Date: Sat, 25 May 2024 18:29:23 +0100	[thread overview]
Message-ID: <20240525182923.490475e5@jic23-huawei> (raw)
In-Reply-To: <20240524124851.567485-1-inv.git-commit@tdk.com>

On Fri, 24 May 2024 12:48:51 +0000
inv.git-commit@tdk.com wrote:

> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> 
> ODR switching happens in 2 steps, update to store the new value and then
> apply when the ODR change flag is received in the data. When switching to
> the same ODR value, the ODR change flag is never happening, and frequency
> switching is blocked waiting for the never coming apply.
> 
> Fix the issue by preventing update to happen when switching to same ODR
> value.
> 
> Fixes: 0ecc363ccea7 ("iio: make invensense timestamp module generic")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>

Applied to the fixes-togreg branch of iio.git

Note I'll rebase that tree on rc1 once available.

> ---
>  drivers/iio/common/inv_sensors/inv_sensors_timestamp.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c b/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> index fa205f17bd90..f44458c380d9 100644
> --- a/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> +++ b/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> @@ -60,11 +60,15 @@ EXPORT_SYMBOL_NS_GPL(inv_sensors_timestamp_init, IIO_INV_SENSORS_TIMESTAMP);
>  int inv_sensors_timestamp_update_odr(struct inv_sensors_timestamp *ts,
>  				     uint32_t period, bool fifo)
>  {
> +	uint32_t mult;
> +
>  	/* when FIFO is on, prevent odr change if one is already pending */
>  	if (fifo && ts->new_mult != 0)
>  		return -EAGAIN;
>  
> -	ts->new_mult = period / ts->chip.clock_period;
> +	mult = period / ts->chip.clock_period;
> +	if (mult != ts->mult)
> +		ts->new_mult = mult;
>  
>  	return 0;
>  }


      reply	other threads:[~2024-05-25 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 12:48 [PATCH] iio: invensense: fix odr switching to same value inv.git-commit
2024-05-25 17:29 ` 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=20240525182923.490475e5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=inv.git-commit@tdk.com \
    --cc=jean-baptiste.maneyrol@tdk.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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