From: sashiko-bot@kernel.org
To: "Michal Wilczynski" <m.wilczynski@samsung.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v6 2/5] phy: Add common Innosilicon HDMI PHY helpers
Date: Wed, 28 Oct 2026 15:30:57 +0000 [thread overview]
Message-ID: <sashiko-outbox-188055@kernel.org> (raw)
In-Reply-To: <20261028-jh7110-inno-hdmi-phy-v6-2-f3379684d97e@samsung.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] phy: inno-hdmi: 32-bit overflow in inno_hdmi_phy_pre_pll_recalc_rate()
--
commit ddb60d944975dab0de39c50bd23d32e884d239ae
Author: Michal Wilczynski <m.wilczynski@samsung.com>
phy: Add common Innosilicon HDMI PHY helpers
This commit introduces a shared helper library for the Innosilicon HDMI PHY
pre-PLL configuration, including table lookup, clock rate calculation helpers,
and register programming.
> diff --git a/drivers/phy/phy-inno-hdmi.c b/drivers/phy/phy-inno-hdmi.c
> new file mode 100644
> index 0000000000000..6900d4d83e464
> --- /dev/null
> +++ b/drivers/phy/phy-inno-hdmi.c
[ ... ]
> +unsigned long
> +inno_hdmi_phy_pre_pll_recalc_rate(const struct inno_hdmi_phy_pre_pll *pll,
> + unsigned long parent_rate)
> +{
> + unsigned int control, div_1, div_2, div_3, pclk_div_ab, pclk_div_cd;
> + unsigned int frac_div_7_0, frac_div_15_8, frac_div_23_16, div;
> + u8 nd, no_a, no_b, no_d;
> + unsigned long frac, rate;
> + u64 vco, vco_rate;
> + u16 nf;
> + int ret;
[ ... ]
> + nd = div_1 & INNO_PRE_PLL_PRE_DIV_MASK;
> + nf = (div_2 & INNO_PRE_PLL_FB_DIV_11_8_MASK) << 8;
> + nf |= div_3;
> + vco = parent_rate * nf;
> +
> + if (!(div_2 & INNO_PRE_PLL_FRAC_DIV_DISABLE)) {
> + ret = inno_read(pll, INNO_PRE_PLL_FRAC_DIV_7_0, &frac_div_7_0);
> + if (ret)
> + goto err;
> + ret = inno_read(pll, INNO_PRE_PLL_FRAC_DIV_15_8, &frac_div_15_8);
> + if (ret)
> + goto err;
> + ret = inno_read(pll, INNO_PRE_PLL_FRAC_DIV_23_16,
> + &frac_div_23_16);
> + if (ret)
> + goto err;
> +
> + frac = frac_div_7_0 | (frac_div_15_8 << 8) |
> + (frac_div_23_16 << 16);
> + vco += DIV_ROUND_CLOSEST(parent_rate * frac,
> + BIT(INNO_FRAC_DIV_WIDTH));
> + }
[Severity: Medium]
Can the VCO calculations in inno_hdmi_phy_pre_pll_recalc_rate() in
drivers/phy/phy-inno-hdmi.c overflow on 32-bit architectures?
Both parent_rate and frac have type unsigned long, while nf is a u16 and vco
is a u64. On 32-bit targets where unsigned long is 32 bits wide,
parent_rate * nf is evaluated in 32-bit arithmetic before being widened to
u64. With a typical 24 MHz reference clock, any feedback divider nf >= 179
exceeds U32_MAX, whereas the 12-bit feedback divider reaches up to 757 in the
Innosilicon pre-PLL configuration tables.
Similarly, when the fractional divider is enabled, parent_rate * frac and
DIV_ROUND_CLOSEST() operate on 32-bit unsigned long values before adding to
vco. For a 24 MHz parent_rate and a 24-bit frac value, parent_rate * frac
requires up to 49 bits and overflows 32-bit unsigned long whenever frac >= 179.
Should parent_rate be cast to u64 in parent_rate * nf, and should the
fractional calculation use DIV_ROUND_CLOSEST_ULL((u64)parent_rate * frac,
BIT(INNO_FRAC_DIV_WIDTH)) to avoid 32-bit truncation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261028-jh7110-inno-hdmi-phy-v6-0-f3379684d97e@samsung.com?part=2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-28 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261028152225eucas1p133ea1b7981dfa2afe085b83e1bd6de3b@eucas1p1.samsung.com>
2026-10-28 15:21 ` [PATCH v6 0/5] phy: Add the StarFive JH7110 Innosilicon HDMI PHY Michal Wilczynski
2026-10-28 15:21 ` [PATCH v6 1/5] dt-bindings: phy: Add starfive,jh7110-inno-hdmi-phy Michal Wilczynski
2026-10-28 15:21 ` [PATCH v6 2/5] phy: Add common Innosilicon HDMI PHY helpers Michal Wilczynski
2026-10-28 15:30 ` sashiko-bot [this message]
2026-10-28 15:21 ` [PATCH v6 3/5] phy: rockchip: inno-hdmi: Use the common Innosilicon " Michal Wilczynski
2026-10-28 15:21 ` [PATCH v6 4/5] phy: starfive: Add jh7110-inno-hdmi-phy driver Michal Wilczynski
2026-10-28 15:46 ` sashiko-bot
2026-10-28 15:21 ` [PATCH v6 5/5] MAINTAINERS: Add StarFive JH7110 HDMI PHY entry Michal Wilczynski
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=sashiko-outbox-188055@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=m.wilczynski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@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