public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Felix Gu <ustc.gu@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] iio: adc: nxp-sar-adc: Avoid division by zero
Date: Fri, 17 Apr 2026 10:41:02 +0200	[thread overview]
Message-ID: <79b02540-7981-4584-aca2-98e1b95cde79@oss.qualcomm.com> (raw)
In-Reply-To: <20260416090122.758990-1-andriy.shevchenko@linux.intel.com>


Hi Andy,

On 4/16/26 11:01, Andy Shevchenko wrote:
> When Common Clock Framework is disabled, clk_get_rate() returns 0.
> This is used as part of the divisor to perform nanosecond delays
> with help of ndelay(). When the above condition occurs the compiler,
> due to unspecified behaviour, is free to do what it wants to. Here
> it saturates the value, which is logical from mathematics point of
> view. However, the ndelay() implementation has set a reasonable
> upper threshold and refuses to provide anything for such a long
> delay. That's why code may not be linked under these circumstances.
> 
> To solve the issue, provide a wrapper that calls ndelay() when
> the value is known not to be zero.
> 
> Fixes: 4434072a893e ("iio: adc: Add the NXP SAR ADC support for the s32g2/3 platforms")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202603311958.ly6uROit-lkp@intel.com/
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Acked-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>

> ---
>   drivers/iio/adc/nxp-sar-adc.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/adc/nxp-sar-adc.c b/drivers/iio/adc/nxp-sar-adc.c
> index 9d9f2c76bed4..705dd7da1bd2 100644
> --- a/drivers/iio/adc/nxp-sar-adc.c
> +++ b/drivers/iio/adc/nxp-sar-adc.c
> @@ -198,6 +198,15 @@ 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)
> +{
> +	u64 rate;
> +
> +	rate = clk_get_rate(info->clk);
> +	if (rate)
> +		ndelay(div64_u64(NSEC_PER_SEC, rate * cycles));
> +}
> +
>   static bool nxp_sar_adc_set_enabled(struct nxp_sar_adc *info, bool enable)
>   {
>   	u32 mcr;
> @@ -221,7 +230,7 @@ static bool nxp_sar_adc_set_enabled(struct nxp_sar_adc *info, bool enable)
>   	 * configuration of NCMR and the setting of NSTART.
>   	 */
>   	if (enable)
> -		ndelay(div64_u64(NSEC_PER_SEC, clk_get_rate(info->clk) * 3));
> +		nxp_sar_adc_wait_for(info, 3);
>   
>   	return pwdn;
>   }
> @@ -469,7 +478,7 @@ static void nxp_sar_adc_stop_conversion(struct nxp_sar_adc *info)
>   	 * only when the capture finishes. The delay will be very
>   	 * short, usec-ish, which is acceptable in the atomic context.
>   	 */
> -	ndelay(div64_u64(NSEC_PER_SEC, clk_get_rate(info->clk)) * 80);
> +	nxp_sar_adc_wait_for(info, 80);
>   }
>   
>   static int nxp_sar_adc_start_conversion(struct nxp_sar_adc *info, bool raw)


      reply	other threads:[~2026-04-17  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16  9:01 [PATCH v1 1/1] iio: adc: nxp-sar-adc: Avoid division by zero Andy Shevchenko
2026-04-17  8:41 ` Daniel Lezcano [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=79b02540-7981-4584-aca2-98e1b95cde79@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nuno.sa@analog.com \
    --cc=ustc.gu@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