Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	<intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 11/13] drm/i915: Carve intel_atomic_commit_type() up a bit
Date: Wed, 16 Sep 2026 18:55:17 +0530	[thread overview]
Message-ID: <0e70bfe1-8da7-43b9-bab4-31b2c93aa92f@intel.com> (raw)
In-Reply-To: <20260909161730.12969-12-ville.syrjala@linux.intel.com>



On 9/9/2026 9:47 PM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> We can't currently do full modesets, fastsets, nor async
> flips via either DSB nor flip qeueu. Let's checks for those
> up front to reduce the clutter in the if statements.
> 

typo: queue, check

> And while at it, throw in some TODO comments to remind
> us that we may want to implement these via DSB/flip queue
> eventually.
> 

Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>

> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_display.c | 22 +++++++++++++-------
>   1 file changed, 14 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 9a24eb16025a..eea2c2b40304 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -7388,21 +7388,27 @@ intel_atomic_commit_type(struct intel_atomic_state *state,
>   	if (state->base.legacy_cursor_update)
>   		return INTEL_COMMIT_MMIO;
>   
> -	/* FIXME deal with everything */
> +	/* TODO maybe enable/disable planes via DSB/flip queue during modeset? */
> +	if (intel_crtc_needs_modeset(new_crtc_state))
> +		return INTEL_COMMIT_MMIO;
> +
> +	/* TODO implement fastsets via DSB/flip queue */
> +	if (intel_crtc_needs_fastset(new_crtc_state))
> +		return INTEL_COMMIT_MMIO;
> +
> +	/* TODO implement async flips via DSB/flip queue */
> +	if (new_crtc_state->do_async_flip)
> +		return INTEL_COMMIT_MMIO;
> +
> +	/* TODO handle VRR with flip queue */
>   	if (intel_flipq_supported(display) &&
> -	    !new_crtc_state->do_async_flip &&
>   	    !new_crtc_state->vrr.enable &&
>   	    !new_crtc_state->has_psr &&
> -	    !intel_crtc_needs_modeset(new_crtc_state) &&
> -	    !intel_crtc_needs_fastset(new_crtc_state) &&
>   	    !intel_crtc_needs_color_update(new_crtc_state))
>   		return INTEL_COMMIT_FLIPQ;
>   
>   	if (intel_dsb_supported(display) &&
> -	    !new_crtc_state->do_async_flip &&
> -	    (DISPLAY_VER(display) >= 20 || !new_crtc_state->has_psr) &&
> -	    !intel_crtc_needs_modeset(new_crtc_state) &&
> -	    !intel_crtc_needs_fastset(new_crtc_state))
> +	    (DISPLAY_VER(display) >= 20 || !new_crtc_state->has_psr))
>   		return INTEL_COMMIT_DSB;
>   
>   	return INTEL_COMMIT_MMIO;


  reply	other threads:[~2026-09-16 13:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 16:17 [PATCH v2 00/13] drm/i915: Some DSB/flipq stuff Ville Syrjala
2026-09-09 16:17 ` [PATCH v2 01/13] drm/i915: Give up on DSB/flip queue if we fail to allocate the color DSB buffer Ville Syrjala
2026-09-16 13:22   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 02/13] drm/i915: Check use_flipq in intel_crtc_needs_vblank_work() Ville Syrjala
2026-09-16 13:22   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 03/13] drm/i915: Don't initialize flip queue on pre-LNL Ville Syrjala
2026-09-16 13:22   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 04/13] drm/i915: Warn about use_flip==true in MMIO commit codepaths Ville Syrjala
2026-09-16 13:22   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 05/13] drm/i915: Refine vblank evasion DSB check Ville Syrjala
2026-09-16 13:23   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 06/13] drm/i915: Make intel_crtc_needs_vblank_work() easier on the eye Ville Syrjala
2026-09-16 13:22   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 07/13] drm/i915: Extract intel_dsb_supported() Ville Syrjala
2026-09-16 13:23   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 08/13] drm/i915: Use intel_dsb_supported() to determine 'use_dsb' Ville Syrjala
2026-09-16 13:24   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 09/13] drm/i915: Extract commit_dsb_max_cmds() Ville Syrjala
2026-09-16 13:23   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 10/13] drm/i915: Introduce enum intel_commit_type Ville Syrjala
2026-09-16 13:24   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 11/13] drm/i915: Carve intel_atomic_commit_type() up a bit Ville Syrjala
2026-09-16 13:25   ` Borah, Chaitanya Kumar [this message]
2026-09-09 16:17 ` [PATCH v2 12/13] drm/i915/dsb: Add tracepoints for DSB commit Ville Syrjala
2026-09-09 16:34   ` sashiko-bot
2026-09-10 11:23     ` Ville Syrjälä
2026-09-16 13:25   ` Borah, Chaitanya Kumar
2026-09-09 16:17 ` [PATCH v2 13/13] drm/i915/dsb: Add tracepoints for flip queue Ville Syrjala
2026-09-16 13:25   ` Borah, Chaitanya Kumar
2026-09-09 17:50 ` ✓ i915.CI.BAT: success for drm/i915: Some DSB/flipq stuff (rev2) Patchwork
2026-09-10 10:56 ` ✗ i915.CI.Full: failure " 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=0e70bfe1-8da7-43b9-bab4-31b2c93aa92f@intel.com \
    --to=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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