From: Brian Masney <bmasney@redhat.com>
To: "Pavel Löbl" <pavel@loebl.cz>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michal Simek <michal.simek@amd.com>,
linux-clk@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] clk: clocking-wizard: fix integer overflow in rate calculation
Date: Mon, 15 Jun 2026 12:32:39 -0400 [thread overview]
Message-ID: <ajApJ5RDcffKtZOH@redhat.com> (raw)
In-Reply-To: <20260605130340.3549582-1-pavel@loebl.cz>
On Fri, Jun 05, 2026 at 03:03:40PM +0200, Pavel Löbl wrote:
> When using driver on Zynq-7000 (32-bit) determine_rate calculation
> overflows. For instance requesting 32MHz with 100MHz parent clock
> results in 100000000*(4*1000+0) 32-bit multiplication.
>
> Replace the expression with mult_frac which is already used in
> clk_wzrd_recalc_ratef.
>
> Cc: stable@vger.kernel.org
> Fixes: 7681f64e6404 ("clk: clocking-wizard: calculate dividers fractional parts")
> Signed-off-by: Pale Löbl <pavel@loebl.cz>
Reviewed-by: Brian Masney <bmasney@redhat.com>
prev parent reply other threads:[~2026-06-15 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 13:03 [PATCH] clk: clocking-wizard: fix integer overflow in rate calculation Pavel Löbl
2026-06-15 16:32 ` Brian Masney [this message]
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=ajApJ5RDcffKtZOH@redhat.com \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=pavel@loebl.cz \
--cc=sboyd@kernel.org \
--cc=stable@vger.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