From: Brian Masney <bmasney@redhat.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v4 1/2] clk: divider: Add KUnit tests for clk_divider_bestdiv() ULONG_MAX handling
Date: Mon, 27 Apr 2026 11:23:21 -0400 [thread overview]
Message-ID: <ae9_afsqmGDcczhW@redhat.com> (raw)
In-Reply-To: <20260427112824.231150-2-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi Lad,
On Mon, Apr 27, 2026 at 12:28:23PM +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add KUnit tests to verify the behaviour of clk_divider_bestdiv() when
> clk_round_rate() is called with ULONG_MAX, which is the canonical way
> to probe the maximum rate a clock can produce.
>
> Two test cases are introduced:
>
> - clk_divider_bestdiv_ulong_max_returns_max_rate: registers a 1 GHz
> fixed-rate parent driving a table-based divider whose smallest entry
> is div=2 (entries: 2, 4, 8). Calls clk_hw_round_rate(div_hw, ULONG_MAX)
> and checks the result.
>
> - clk_divider_bestdiv_mux_ulong_max_returns_max_rate: places a two-input
> mux (4 GHz and 2 GHz fixed-rate parents, CLK_SET_RATE_PARENT) ahead of
> the same table-based divider to verify correct parent selection under
> ULONG_MAX.
>
> Both tests use an explicit clk_div_table with a minimum divider of 2 so
> that the pre-loop maxdiv clamping in clk_divider_bestdiv():
>
> maxdiv = min(ULONG_MAX / rate, maxdiv);
>
> clamps maxdiv to 1, causing _next_div() to return 2 on the first
> iteration and skip the loop body entirely. This makes bestdiv fall back
> to the maximum divider, returning the minimum rate rather than the
> maximum.
>
> The expected values intentionally reflect the buggy output:
> - test 1: PARENT_RATE_1GHZ / 8 (minimum rate, not maximum)
> - test 2: 0 (invalid, loop never populated bestdiv)
>
> These will be corrected to PARENT_RATE_1GHZ / 2 and PARENT_RATE_4GHZ / 2
> respectively once the fix to clk_divider_bestdiv() is applied.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
[snip]
> + KUNIT_ASSERT_EQ(test, 0,
> + kunit_add_action_or_reset(test,
> + (kunit_action_t *)clk_hw_unregister_fixed_rate,
> + parent_hw));
You can use KUNIT_DEFINE_ACTION_WRAPPER() to avoid that cast. There's
some examples in drivers/clk/clk_kunit_helpers.c.
With that fixed:
Reviewed-by: Brian Masney <bmasney@redhat.com>
next prev parent reply other threads:[~2026-04-27 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 11:28 [PATCH v4 0/2] Fix clk_divider_bestdiv() to get max clk rate supported and add KUnit test suites Prabhakar
2026-04-27 11:28 ` [PATCH v4 1/2] clk: divider: Add KUnit tests for clk_divider_bestdiv() ULONG_MAX handling Prabhakar
2026-04-27 15:23 ` Brian Masney [this message]
2026-04-27 19:40 ` Lad, Prabhakar
2026-04-27 11:28 ` [PATCH v4 2/2] clk: divider: Fix clk_divider_bestdiv() returning min rate for large rate requests Prabhakar
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=ae9_afsqmGDcczhW@redhat.com \
--to=bmasney@redhat.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sboyd@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