From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Dibin Moolakadan Subrahmanian
<dibin.moolakadan.subrahmanian@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915/display: Fix intel_snps_hdmi_pll.c overflow issues
Date: Tue, 27 May 2025 10:18:42 +0530 [thread overview]
Message-ID: <513ccbae-a5bf-4e90-807f-855d9973041d@intel.com> (raw)
In-Reply-To: <20250513083803.2596286-3-dibin.moolakadan.subrahmanian@intel.com>
On 5/13/2025 2:08 PM, Dibin Moolakadan Subrahmanian wrote:
> intel_snps_hdmi_pll.c calls do_div function from DIV_ROUND_UP_ULL
I think you can remove the file name from subject and commit message.
> and DIV_ROUND_DOWN_ULL macros. do_div expects the arg2 type to be u32.
> On higher data rate arg2 exceeds u32 and ends up in wrong pll
> configuration.
>
> So change do_div calls to div64_base64 calls where ever arg2 exceeds u32.
Add fixes tag:
Fixes: 5947642004bf ("drm/i915/display: Add support for SNPS PHY HDMI
PLL algorithm for DG2")
Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
With the above changes this is:
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c b/drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c
> index 41c6c111af1d..74bb3bedf30f 100644
> --- a/drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c
> +++ b/drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c
> @@ -41,9 +41,9 @@ static s64 interp(s64 x, s64 x1, s64 x2, s64 y1, s64 y2)
> {
> s64 dydx;
>
> - dydx = DIV_ROUND_UP_ULL((y2 - y1) * 100000, (x2 - x1));
> + dydx = DIV64_U64_ROUND_UP((y2 - y1) * 100000, (x2 - x1));
>
> - return (y1 + DIV_ROUND_UP_ULL(dydx * (x - x1), 100000));
> + return (y1 + DIV64_U64_ROUND_UP(dydx * (x - x1), 100000));
> }
>
> static void get_ana_cp_int_prop(u64 vco_clk,
> @@ -115,16 +115,16 @@ static void get_ana_cp_int_prop(u64 vco_clk,
> CURVE0_MULTIPLIER));
>
> scaled_interpolated_sqrt =
> - int_sqrt(DIV_ROUND_UP_ULL(interpolated_product, vco_div_refclk_float) *
> + int_sqrt(DIV64_U64_ROUND_UP(interpolated_product, vco_div_refclk_float) *
> DIV_ROUND_DOWN_ULL(1000000000000ULL, 55));
>
> /* Scale vco_div_refclk for ana_cp_int */
> scaled_vco_div_refclk2 = DIV_ROUND_UP_ULL(vco_div_refclk_float, 1000000);
> - adjusted_vco_clk2 = 1460281 * DIV_ROUND_UP_ULL(scaled_interpolated_sqrt *
> + adjusted_vco_clk2 = 1460281 * DIV64_U64_ROUND_UP(scaled_interpolated_sqrt *
> scaled_vco_div_refclk2,
> curve_1_interpolated);
>
> - *ana_cp_prop = DIV_ROUND_UP_ULL(adjusted_vco_clk2, curve_2_scaled2);
> + *ana_cp_prop = DIV64_U64_ROUND_UP(adjusted_vco_clk2, curve_2_scaled2);
> *ana_cp_prop = max(1, min(*ana_cp_prop, 127));
> }
>
> @@ -165,10 +165,10 @@ static void compute_hdmi_tmds_pll(u64 pixel_clock, u32 refclk,
> /* Select appropriate v2i point */
> if (datarate <= INTEL_SNPS_PHY_HDMI_9999MHZ) {
> mpll_ana_v2i = 2;
> - tx_clk_div = ilog2(DIV_ROUND_DOWN_ULL(INTEL_SNPS_PHY_HDMI_9999MHZ, datarate));
> + tx_clk_div = ilog2(div64_u64(INTEL_SNPS_PHY_HDMI_9999MHZ, datarate));
> } else {
> mpll_ana_v2i = 3;
> - tx_clk_div = ilog2(DIV_ROUND_DOWN_ULL(INTEL_SNPS_PHY_HDMI_16GHZ, datarate));
> + tx_clk_div = ilog2(div64_u64(INTEL_SNPS_PHY_HDMI_16GHZ, datarate));
> }
> vco_clk = (datarate << tx_clk_div) >> 1;
>
next prev parent reply other threads:[~2025-05-27 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:38 [PATCH 0/2] Fix u32 overflow issues for SNPS PHY HDMI PLL Dibin Moolakadan Subrahmanian
2025-05-13 8:38 ` [PATCH 1/2] drm/i915/display: Fix get_ana_cp_int_prop() argument type Dibin Moolakadan Subrahmanian
2025-05-27 4:50 ` Nautiyal, Ankit K
2025-05-13 8:38 ` [PATCH 2/2] drm/i915/display: Fix intel_snps_hdmi_pll.c overflow issues Dibin Moolakadan Subrahmanian
2025-05-27 4:48 ` Nautiyal, Ankit K [this message]
2025-05-14 7:08 ` ✓ CI.Patch_applied: success for Fix u32 overflow issues for SNPS PHY HDMI PLL Patchwork
2025-05-14 7:09 ` ✓ CI.checkpatch: " Patchwork
2025-05-14 7:10 ` ✓ CI.KUnit: " Patchwork
2025-05-14 7:20 ` ✓ CI.Build: " Patchwork
2025-05-14 7:23 ` ✓ CI.Hooks: " Patchwork
2025-05-14 7:24 ` ✓ CI.checksparse: " Patchwork
2025-05-14 8:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-14 10:10 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 22:37 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-26 22:37 ` ✓ CI.checkpatch: " Patchwork
2025-05-26 22:38 ` ✓ CI.KUnit: " Patchwork
2025-05-26 22:49 ` ✓ CI.Build: " Patchwork
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=513ccbae-a5bf-4e90-807f-855d9973041d@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=dibin.moolakadan.subrahmanian@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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