From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/i915/display: Move casf_compute_config
Date: Thu, 12 Mar 2026 08:43:15 +0530 [thread overview]
Message-ID: <70c9125a-e553-4fa5-adc4-ed4012b013ae@intel.com> (raw)
In-Reply-To: <20251223081300.1196417-2-nemesa.garg@intel.com>
On 12/23/2025 1:42 PM, Nemesa Garg wrote:
> Prefill calculations are getting screwed up as casf_compute
> is getting called in later stage. So move casf_compute_config
> to crtc_compute_config and check if there is a change in the
> sharpness strength, if so set the flag uapi.mode_changed
> so that everytime when strength changes casf_compute_config
> can be called and new strength value gets updated.
Nit: Please wrap the commit message to ~75 characters as per kernel
guidelines.
Patch looks good to me.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>
> v2: Remove extra casf_check [Ville]
>
> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 9c6d3ecdb589..568730ffe359 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -2494,6 +2494,10 @@ static int intel_crtc_compute_config(struct intel_atomic_state *state,
>
> intel_vrr_compute_guardband(crtc_state);
>
> + ret = intel_casf_compute_config(crtc_state);
> + if (ret)
> + return ret;
> +
> return 0;
> }
>
> @@ -4286,10 +4290,6 @@ static int intel_crtc_atomic_check(struct intel_atomic_state *state,
> return ret;
> }
>
> - ret = intel_casf_compute_config(crtc_state);
> - if (ret)
> - return ret;
> -
> if (DISPLAY_VER(display) >= 9) {
> if (intel_crtc_needs_modeset(crtc_state) ||
> intel_crtc_needs_fastset(crtc_state) ||
> @@ -6431,6 +6431,10 @@ int intel_atomic_check(struct drm_device *dev,
> if (new_crtc_state->uapi.scaling_filter !=
> old_crtc_state->uapi.scaling_filter)
> new_crtc_state->uapi.mode_changed = true;
> +
> + if (new_crtc_state->uapi.sharpness_strength !=
> + old_crtc_state->uapi.sharpness_strength)
> + new_crtc_state->uapi.mode_changed = true;
> }
>
> intel_vrr_check_modeset(state);
next prev parent reply other threads:[~2026-03-12 3:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 8:12 [PATCH 0/3] Make casf updates atomic and dsb ready Nemesa Garg
2025-12-23 8:12 ` [PATCH 1/3] drm/i915/display: Move casf_compute_config Nemesa Garg
2026-03-12 3:13 ` Nautiyal, Ankit K [this message]
2025-12-23 8:12 ` [PATCH 2/3] drm/i915/display: Introduce skl_pipe_scaler_setup() Nemesa Garg
2026-03-12 4:30 ` Nautiyal, Ankit K
2025-12-23 8:13 ` [PATCH 3/3] drm/i915/display: Common wrapper for casf and pfit Nemesa Garg
2026-03-12 11:19 ` Nautiyal, Ankit K
2025-12-23 9:14 ` ✗ i915.CI.BAT: failure for Make casf updates atomic and dsb ready (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-03-26 12:00 [PATCH 0/3] Make casf updates atomic and dsb ready Nemesa Garg
2026-03-26 12:00 ` [PATCH 1/3] drm/i915/display: Move casf_compute_config Nemesa Garg
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=70c9125a-e553-4fa5-adc4-ed4012b013ae@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nemesa.garg@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