Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, rodrigo.vivi@intel.com,
	suraj.kandpal@intel.com, ankit.k.nautiyal@intel.com,
	nathan@kernel.org
Subject: Re: [PATCH] drm/i915/display: Consider adjusted_pixel_rate to be u64
Date: Mon, 24 Jun 2024 12:50:20 +0300	[thread overview]
Message-ID: <87pls6ekkj.fsf@intel.com> (raw)
In-Reply-To: <20240621073454.1421676-1-mitulkumar.ajitkumar.golani@intel.com>

On Fri, 21 Jun 2024, Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> wrote:
> Consider adjusted_pixel_rate to be a u64 to match the return
> type of mul_u32_u32() and avoid any compiler dependency for
> do_div.

You should mention this fixes 32-bit builds. Might also want to give a
link to the actual build failure, and give credit to the reporter:

Closes: https://lore.kernel.org/r/20240619154207.GA1125704@thelio-3990X
Reported-by: Nathan Chancellor <nathan@kernel.org>

>
> Fixes: 1676ecd303ac ("drm/i915: Compute CMRR and calculate vtotal")
> Cc: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Cc: Suraj Kandpal <suraj.kandpal@intel.com>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: intel-xe@lists.freedesktop.org
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_vrr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index 6430da25957d..5a0da64c7db3 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -137,7 +137,7 @@ static unsigned int
>  cmrr_get_vtotal(struct intel_crtc_state *crtc_state, bool video_mode_required)
>  {
>  	int multiplier_m = 1, multiplier_n = 1, vtotal, desired_refresh_rate;
> -	long long adjusted_pixel_rate;
> +	u64 adjusted_pixel_rate;
>  	struct drm_display_mode *adjusted_mode = &crtc_state->hw.adjusted_mode;
>  
>  	desired_refresh_rate = drm_mode_vrefresh(adjusted_mode);

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2024-06-24  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  7:34 [PATCH] drm/i915/display: Consider adjusted_pixel_rate to be u64 Mitul Golani
2024-06-21  8:09 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-21  8:09 ` ✓ CI.checkpatch: " Patchwork
2024-06-21  8:10 ` ✓ CI.KUnit: " Patchwork
2024-06-21  8:22 ` ✓ CI.Build: " Patchwork
2024-06-21  8:24 ` ✗ CI.Hooks: failure " Patchwork
2024-06-21  8:26 ` ✗ CI.checksparse: warning " Patchwork
2024-06-21  8:49 ` ✓ CI.BAT: success " Patchwork
2024-06-21 10:19 ` ✗ CI.FULL: failure " Patchwork
2024-06-21 14:32 ` [PATCH] " Rodrigo Vivi
2024-06-24  9:50 ` Jani Nikula [this message]
2024-06-24 10:07 ` Kandpal, Suraj

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=87pls6ekkj.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mitulkumar.ajitkumar.golani@intel.com \
    --cc=nathan@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=suraj.kandpal@intel.com \
    /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