From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
greghk@linuxfoundation.org, dlechner@baylibre.com,
nono.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] iio: frequency: ad983x: replace do_div() with div64_ul().
Date: Thu, 9 Apr 2026 18:49:00 +0300 [thread overview]
Message-ID: <adfKbAyEO0K1p9Vu@ashevche-desk.local> (raw)
In-Reply-To: <20260409131823.1289-1-joshua.crofts1@gmail.com>
On Thu, Apr 09, 2026 at 01:18:23PM +0000, Joshua Crofts wrote:
> Coccinelle reported the following in both ad983x drivers:
> do_div() does a 64-by-32 division, please consider using
> div64_ul instead.
div64_ul()
> Fix this by replacing do_div() with div64_ul(), which
> safely handles 64-bit dividends and unsigned long
> divisors across all architectures.
You should really dive into this code, it has more to work on...
...
> #include <linux/device.h>
> #include <linux/err.h>
> #include <linux/kernel.h>
Consider replacing "proxy" headers at some point. (Not related to this patch,
though.)
> +#include <linux/math64.h>
> #include <linux/module.h>
> #include <linux/regulator/consumer.h>
> #include <linux/slab.h>
...
> static unsigned long ad9832_calc_freqreg(unsigned long mclk, unsigned long fout)
> {
> unsigned long long freqreg = (u64)fout *
> (u64)((u64)1L << AD9832_FREQ_BITS);
(u64)1L is a fancy way of doing 1ULL. The second (u64) is also redundant and
altogether it's just a BIT_ULL(). But, check the value of _FREQ_BITS. If it's less than 32, the whole train of nonsense can be collapsed just to a BIT().
> - do_div(freqreg, mclk);
> + freqreg = div64_ul(freqreg, mclk);
> return freqreg;
> }
...
> --- a/drivers/staging/iio/frequency/ad9834.c
> +++ b/drivers/staging/iio/frequency/ad9834.c
> @@ -10,6 +10,7 @@
> #include <linux/workqueue.h>
> #include <linux/device.h>
> #include <linux/kernel.h>
> +#include <linux/math64.h>
Side note as per above.
> #include <linux/slab.h>
> #include <linux/sysfs.h>
> #include <linux/list.h>
> @@ -101,7 +102,7 @@ static unsigned int ad9834_calc_freqreg(unsigned long mclk, unsigned long fout)
> {
> unsigned long long freqreg = (u64)fout * (u64)BIT(AD9834_FREQ_BITS);
>
> - do_div(freqreg, mclk);
> + freqreg = div64_ul(freqreg, mclk);
> return freqreg;
> }
Ditto. Also split changes on per-driver basis.
...
So, if you go suggested way, I would expect to have 4 patches (2 series by 2
patches each) out of this one.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-09 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:18 [PATCH] iio: frequency: ad983x: replace do_div() with div64_ul() Joshua Crofts
2026-04-09 13:34 ` Joshua Crofts
2026-04-09 14:52 ` Greg KH
2026-04-09 15:01 ` [PATCH v2] " Joshua Crofts
2026-04-09 15:39 ` David Lechner
2026-04-09 15:50 ` Andy Shevchenko
2026-04-09 15:49 ` Andy Shevchenko [this message]
2026-04-09 17:27 ` [PATCH] " David Laight
2026-04-09 19:58 ` Joshua Crofts
2026-04-09 21:46 ` David Laight
2026-04-10 4:30 ` Andy Shevchenko
2026-04-10 6:58 ` Joshua Crofts
2026-04-10 8:11 ` David Laight
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=adfKbAyEO0K1p9Vu@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=greghk@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nono.sa@analog.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