Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Daniel Lezcano" <daniel.lezcano@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v1 1/1] iio: adc: nxp-sar-adc: Fix the delay calculation in nxp_sar_adc_wait_for()
Date: Fri, 22 May 2026 18:35:33 +0100	[thread overview]
Message-ID: <20260522183533.358a1f30@jic23-huawei> (raw)
In-Reply-To: <20260519215607.78241-1-andriy.shevchenko@linux.intel.com>

On Tue, 19 May 2026 23:56:06 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> The original code was using ndelay() twice. In one case the delay
> is calculated as 1/3 of ADC clock and in the other as 80 ADC clocks.
> But according to the comments in all cases it should be a multiplier
> of the ADC clock, and not a fraction of it. Inadvertently
> nxp_sar_adc_wait_for() takes the wrong case and spread it over
> the code make it wrong in all places. Fix this by modifying a helper
> to correctly use the multiplier.
> 
> Fixes: 7e5c0f97c66a ("iio: adc: nxp-sar-adc: Avoid division by zero")
> Fixes: 4434072a893e ("iio: adc: Add the NXP SAR ADC support for the s32g2/3 platforms")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20260416090122.758990-1-andriy.shevchenko%40linux.intel.com
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Daniel, could you take a look at this one.

Explanation seems fine but original patch was yours so I'd like
some 'aware' eyes on it!

> ---
>  drivers/iio/adc/nxp-sar-adc.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/adc/nxp-sar-adc.c b/drivers/iio/adc/nxp-sar-adc.c
> index 01f3da56e987..68d237ef30c2 100644
> --- a/drivers/iio/adc/nxp-sar-adc.c
> +++ b/drivers/iio/adc/nxp-sar-adc.c
> @@ -198,13 +198,13 @@ static void nxp_sar_adc_irq_cfg(struct nxp_sar_adc *info, bool enable)
>  		writel(0, NXP_SAR_ADC_IMR(info->regs));
>  }
>  
> -static void nxp_sar_adc_wait_for(struct nxp_sar_adc *info, unsigned int cycles)
> +static void nxp_sar_adc_wait_for(struct nxp_sar_adc *info, u64 cycles)
>  {
>  	u64 rate;
>  
>  	rate = clk_get_rate(info->clk);
>  	if (rate)
> -		ndelay(div64_u64(NSEC_PER_SEC, rate * cycles));
> +		ndelay(div64_u64(NSEC_PER_SEC * cycles, rate));
>  }
>  
>  static bool nxp_sar_adc_set_enabled(struct nxp_sar_adc *info, bool enable)


  parent reply	other threads:[~2026-05-22 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 21:56 [PATCH v1 1/1] iio: adc: nxp-sar-adc: Fix the delay calculation in nxp_sar_adc_wait_for() Andy Shevchenko
2026-05-20 11:42 ` Stepan Ionichev
2026-05-22 17:35 ` Jonathan Cameron [this message]
2026-05-26 12:48   ` Daniel Lezcano
2026-07-03 19:06     ` Jonathan Cameron
2026-07-03 20:42       ` Daniel Lezcano
2026-07-03 22:55         ` 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=20260522183533.358a1f30@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sashiko-bot@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