From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Archit Anant <architanant5@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: impedance-analyzer: ad5933: use div64_ul() instead of do_div()
Date: Thu, 22 Jan 2026 17:15:42 +0200 [thread overview]
Message-ID: <aXI_HnvDNbX68-lq@smile.fi.intel.com> (raw)
In-Reply-To: <aXI-ZV4uAd5GyFLz@smile.fi.intel.com>
On Thu, Jan 22, 2026 at 05:12:42PM +0200, Andy Shevchenko wrote:
> On Thu, Jan 22, 2026 at 08:26:33PM +0530, Archit Anant wrote:
...
> > - freqreg = (u64)freq * (u64)(1 << 27);
> > - do_div(freqreg, st->mclk_hz / 4);
> > + freqreg = div64_ul((u64)freq * (u64)(1 << 27),
> > + st->mclk_hz / 4);
>
> It can be one line to begin with.
> Then drop that ugly castings and explicit big shifts.
>
> freqreg = div64_ul(BIT_ULL(27) * freq, st->mclk_hz / 4);
>
> Now you can see That 4 is only 2 bits, so this can be written in
> simpler way:
>
> freqreg = div64_ul(BIT_ULL(29) * freq, st->mclk_hz);
>
> which may give a better precision at the end of the day.
It also might be worth to add a comment on top to explain (with given context
I don't know if there is already one on top of the function, though).
And I think we want AD people to comment on this and maybe explain better
the calculations done (and why the original code drops precision, was it
deliberate?).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-22 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 14:56 [PATCH] staging: iio: impedance-analyzer: ad5933: use div64_ul() instead of do_div() Archit Anant
2026-01-22 15:12 ` Andy Shevchenko
2026-01-22 15:15 ` Andy Shevchenko [this message]
[not found] ` <CADJHxWB3b+bH2+HBP+SG0jxhGNcozstBeWeDH_3dgS-4c2G-6g@mail.gmail.com>
2026-01-22 18:03 ` Andy Shevchenko
2026-02-16 15:52 ` Archit Anant
2026-02-16 19:02 ` David Lechner
2026-02-16 19:04 ` David Lechner
2026-02-17 16:46 ` Archit Anant
2026-02-18 18:19 ` Jonathan Cameron
2026-02-18 18:36 ` Archit Anant
2026-02-17 8:29 ` Andy Shevchenko
2026-02-17 16:31 ` Archit Anant
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=aXI_HnvDNbX68-lq@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=architanant5@gmail.com \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.