From: Cristian Marussi <cristian.marussi@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
sudeep.holla@arm.com, philip.radford@arm.com,
james.quinlan@broadcom.com, f.fainelli@gmail.com,
vincent.guittot@linaro.org, etienne.carriere@foss.st.com,
peng.fan@oss.nxp.com, michal.simek@amd.com,
dan.carpenter@linaro.org, geert+renesas@glider.be,
kuninori.morimoto.gx@renesas.com, marek.vasut+renesas@gmail.com
Subject: Re: [PATCH 01/11] firmware: arm_scmi: Add clock determine_rate operation
Date: Tue, 3 Mar 2026 12:46:50 +0000 [thread overview]
Message-ID: <aabYOiZvYYOypV0A@pluto> (raw)
In-Reply-To: <CAMuHMdUZjZvhifzh0W2wbMZf2DYgZjO=gXepsS2nQtSG0weCag@mail.gmail.com>
On Mon, Mar 02, 2026 at 01:37:00PM +0100, Geert Uytterhoeven wrote:
> Hi Cristian,
>
> On Fri, 27 Feb 2026 at 16:33, Cristian Marussi <cristian.marussi@arm.com> wrote:
> > Add a clock operation to help determining the effective rate, closest to
> > the required one, that a specific clock can support.
> >
> > Calculation is currently performed kernel side and the logic is taken
> > directly from the SCMI Clock driver: embedding the determinate rate logic
> > in the protocol layer enables semplifications in the SCMI Clock protocol
> > interface and will more easily accommodate further evolutions where such
> > determine_rate logic into is optionally delegated to the platform SCMI
> > server.
> >
> > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
>
> Thanks for your patch!
Hi,
thanks for having a look.
>
> > --- a/drivers/firmware/arm_scmi/clock.c
> > +++ b/drivers/firmware/arm_scmi/clock.c
> > @@ -624,6 +625,46 @@ static int scmi_clock_rate_set(const struct scmi_protocol_handle *ph,
> > return ret;
> > }
> >
> > +static int scmi_clock_determine_rate(const struct scmi_protocol_handle *ph,
> > + u32 clk_id, unsigned long *rate)
> > +{
> > + u64 fmin, fmax, ftmp;
> > + struct scmi_clock_info *clk;
> > + struct clock_info *ci = ph->get_priv(ph);
> > +
> > + if (!rate)
> > + return -EINVAL;
> > +
> > + clk = scmi_clock_domain_lookup(ci, clk_id);
> > + if (IS_ERR(clk))
> > + return PTR_ERR(clk);
> > +
> > + /*
> > + * If we can't figure out what rate it will be, so just return the
> > + * rate back to the caller.
> > + */
> > + if (clk->rate_discrete)
> > + return 0;
> > +
> > + fmin = clk->range.min_rate;
> > + fmax = clk->range.max_rate;
> > + if (*rate <= fmin) {
> > + *rate = fmin;
> > + return 0;
> > + } else if (*rate >= fmax) {
> > + *rate = fmax;
> > + return 0;
> > + }
> > +
> > + ftmp = *rate - fmin;
> > + ftmp += clk->range.step_size - 1; /* to round up */
> > + do_div(ftmp, clk->range.step_size);
>
> step_size is u64, while do_div() truncates it to 32-bit.
Yes, as pointed out also by other reviewers, there are pre-existent bugs
probably in this rounding...this patch was meant only to move the logic
away from the CLK SCMI driver into the SCMI Clock protocol layer since
it enables a few simplification...
In the next V2, I will fix rounding errors by adding a dedicated Fix on
top of the original code, before this 'relocation', so as to make the
backport easier and move the fixed code.
Thanks,
Cristian
next prev parent reply other threads:[~2026-03-03 12:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:32 [PATCH 00/11] SCMI Clock rates discovery rework Cristian Marussi
2026-02-27 15:32 ` [PATCH 01/11] firmware: arm_scmi: Add clock determine_rate operation Cristian Marussi
2026-02-27 16:50 ` Jonathan Cameron
2026-02-28 10:07 ` Cristian Marussi
2026-02-28 0:27 ` Peng Fan
2026-02-28 10:13 ` Cristian Marussi
2026-03-02 12:37 ` Geert Uytterhoeven
2026-03-03 12:46 ` Cristian Marussi [this message]
2026-02-27 15:32 ` [PATCH 02/11] clk: scmi: Use new determine_rate clock operation Cristian Marussi
2026-02-28 0:56 ` Peng Fan
2026-02-28 10:23 ` Cristian Marussi
2026-03-02 17:11 ` Brian Masney
2026-03-03 2:54 ` Peng Fan
2026-03-03 12:47 ` Cristian Marussi
2026-03-02 12:39 ` Geert Uytterhoeven
2026-03-03 12:49 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 03/11] firmware: arm_scmi: Simplify clock rates exposed interface Cristian Marussi
2026-02-28 2:07 ` Peng Fan
2026-02-28 10:34 ` Cristian Marussi
2026-03-02 12:48 ` Geert Uytterhoeven
2026-03-02 13:09 ` Geert Uytterhoeven
2026-03-03 12:42 ` Cristian Marussi
2026-03-03 12:40 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 04/11] clk: scmi: Use new simplified per-clock rate properties Cristian Marussi
2026-02-28 2:12 ` Peng Fan
2026-02-27 15:32 ` [PATCH 05/11] firmware: arm_scmi: Drop unused clock rate interfaces Cristian Marussi
2026-02-28 2:13 ` Peng Fan
2026-02-27 15:32 ` [PATCH 06/11] firmware: arm_scmi: Make clock rates allocation dynamic Cristian Marussi
2026-02-28 2:29 ` Peng Fan
2026-02-28 10:36 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 07/11] firmware: arm_scmi: Harden clock parents discovery Cristian Marussi
2026-02-28 2:39 ` Peng Fan
2026-02-28 10:37 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 08/11] firmware: arm_scmi: Refactor iterators internal allocation Cristian Marussi
2026-02-27 15:32 ` [PATCH 09/11] firmware: arm_scmi: Add bound iterators support Cristian Marussi
2026-02-28 2:44 ` Peng Fan
2026-02-28 2:43 ` Peng Fan (OSS)
2026-02-28 10:42 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 10/11] firmware: arm_scmi: Use bound iterators to minimize discovered rates Cristian Marussi
2026-02-27 16:53 ` Jonathan Cameron
2026-02-28 10:43 ` Cristian Marussi
2026-02-27 15:32 ` [PATCH 11/11] firmware: arm_scmi: Introduce all_rates_get clock operation Cristian Marussi
2026-02-28 2:49 ` Peng Fan
2026-02-28 10:47 ` Cristian Marussi
2026-03-02 7:18 ` Peng Fan
2026-03-02 10:47 ` Cristian Marussi
2026-03-02 13:25 ` [PATCH 00/11] SCMI Clock rates discovery rework Geert Uytterhoeven
2026-03-03 13:08 ` Cristian Marussi
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=aabYOiZvYYOypV0A@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=etienne.carriere@foss.st.com \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=james.quinlan@broadcom.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=michal.simek@amd.com \
--cc=peng.fan@oss.nxp.com \
--cc=philip.radford@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.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