From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Neel Bullywon <neelb2403@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: frequency: adf4350: replace loop with fls_long()
Date: Mon, 16 Mar 2026 14:40:39 +0200 [thread overview]
Message-ID: <abf6RwTHSapCUw52@ashevche-desk.local> (raw)
In-Reply-To: <20260314172006.69744-1-neelb2403@gmail.com>
On Sat, Mar 14, 2026 at 01:20:06PM -0400, Neel Bullywon wrote:
> Address the TODO in adf4350_set_freq() by replacing the iterative
> power-of-2 shift loop with a constant-time bitwise calculation.
>
> By comparing the highest set bits of the target constant and freq
> using fls_long(), we can calculate the required RF divider selection
> in a single step without relying on expensive 64-bit division.
>
> This ensures freq is properly shifted to meet or exceed the minimum
> VCO frequency.
...
> st->r4_rf_div_sel = 0;
> - while (freq < ADF4350_MIN_VCO_FREQ) {
> - freq <<= 1;
> - st->r4_rf_div_sel++;
> + if (freq < ADF4350_MIN_VCO_FREQ) {
> + st->r4_rf_div_sel = fls_long(ADF4350_MIN_VCO_FREQ - 1) - fls_long(freq);
> + if ((freq << st->r4_rf_div_sel) < ADF4350_MIN_VCO_FREQ)
> + st->r4_rf_div_sel++;
> }
>
> + freq <<= st->r4_rf_div_sel;
Yeah, unfortunately it looks like too complicated in comparison with the
original code. Have you checked binary output? My gut feelings that this
gives also a lot of code in addition to.
Little optimisation can be like:
if (freq < ADF4350_MIN_VCO_FREQ) {
st->r4_rf_div_sel = fls_long(ADF4350_MIN_VCO_FREQ - 1) - fls_long(freq);
freq <<= st->r4_rf_div_sel;
if (freq < ADF4350_MIN_VCO_FREQ) {
st->r4_rf_div_sel++;
freq <<= 1;
}
}
but it is still too much.
...
Maybe we simply need to replace TODO with a NOTE explaining that if better algo
is found we can replace.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 2:01 [PATCH] iio: frequency: adf4350: replace loop with order_base_2() Neel Bullywon
2026-03-11 12:07 ` Andy Shevchenko
2026-03-14 17:20 ` [PATCH v2] iio: frequency: adf4350: replace loop with fls_long() Neel Bullywon
2026-03-15 13:00 ` Jonathan Cameron
2026-03-16 12:40 ` Andy Shevchenko [this message]
2026-03-22 11:51 ` Jonathan Cameron
2026-03-16 13:51 ` David Laight
2026-03-16 14:07 ` Andy Shevchenko
2026-03-23 11:08 ` Nuno Sá
2026-03-23 13:31 ` 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=abf6RwTHSapCUw52@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neelb2403@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox