All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 12/14] drm/xe/display: Use async flip for flipping initial fb.
Date: Fri, 27 Sep 2024 18:14:24 +0300	[thread overview]
Message-ID: <ZvbL0GUZ3c5-07qJ@intel.com> (raw)
In-Reply-To: <20240927141404.163317-13-maarten.lankhorst@linux.intel.com>

On Fri, Sep 27, 2024 at 04:14:02PM +0200, Maarten Lankhorst wrote:
> Since memirq requires a ggtt allocation, irqs will be initialised
> later. This means we cannot rely on drm_wait_for_vblank any more as
> it requires interrupts.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> 
> TODO: Check for flip completion?
> ---
>  drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/display/xe_plane_initial.c b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> index 4660db0aecb6..bad074540b55 100644
> --- a/drivers/gpu/drm/xe/display/xe_plane_initial.c
> +++ b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> @@ -17,6 +17,8 @@
>  #include "intel_fb_pin.h"
>  #include "intel_frontbuffer.h"
>  #include "intel_plane_initial.h"
> +#include "intel_uncore.h"
> +#include "skl_universal_plane_regs.h"
>  #include "xe_bo.h"
>  #include "xe_wa.h"
>  
> @@ -187,6 +189,7 @@ static void
>  intel_find_initial_plane_obj(struct intel_crtc *crtc,
>  			     struct intel_initial_plane_config plane_configs[])
>  {
> +	struct xe_device *xe = to_xe_device(crtc->base.dev);
>  	struct intel_initial_plane_config *plane_config =
>  		&plane_configs[crtc->pipe];
>  	struct intel_plane *plane =
> @@ -235,6 +238,10 @@ intel_find_initial_plane_obj(struct intel_crtc *crtc,
>  	plane_state->uapi.crtc = &crtc->base;
>  	intel_plane_copy_uapi_to_hw_state(plane_state, plane_state, crtc);
>  
> +	/* Flip async, we don't have interrupts yet */
> +	plane_state->ctl = intel_uncore_read(&xe->uncore, PLANE_CTL(plane->pipe, PLANE_1));
> +	plane->async_flip(plane, to_intel_crtc_state(crtc->base.state), plane_state, true);
> +
>  	atomic_or(plane->frontbuffer_bit, &to_intel_frontbuffer(fb)->bits);
>  
>  	plane_config->vma = vma;
> @@ -292,9 +299,6 @@ void intel_initial_plane_config(struct drm_i915_private *i915)
>  		 */
>  		intel_find_initial_plane_obj(crtc, plane_configs);
>  
> -		if (i915->display.funcs.display->fixup_initial_plane_config(crtc, plane_config))
> -			intel_crtc_wait_for_next_vblank(crtc);

Argh. I think the best solution would probably be to provide
an intel_crtc_wait_for_next_vblank_early()/etc. that just
falls back to polling the status bit if interrupts aren't
available.

Or we could also just poll the live surface register
instead (though that is not available on ancient hardware
so would have to assert that it's not used there).

I suppose another option might be to just usleep() in
the fallback. This would have the benefit of not needing
any hardware specific implementations. This doesn't really
need to be that accurate as long it guarantees that we
wait for at least one frame duration.

> -
>  		plane_config_fini(plane_config);
>  	}
>  }
> -- 
> 2.45.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-09-27 15:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 14:13 [PATCH 00/14] drm/xe: Fix flickering when inheriting BIOS fb Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 01/14] drm/xe/display: Handle stolen bar readout in the same way as lmem Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 02/14] drm/xe: Remove double pageflip Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 03/14] drm/xe: Move suballocator init to after display init Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 04/14] drm/xe: Initialize UC after xe_display_init_noaccel Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 05/14] drm/xe: Use xe_ggtt_map_bo_unlocked for resume Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 06/14] drm/xe: Add xe_ggtt_might_lock Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 07/14] drm/xe: Add xe_ggtt_alloc Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 08/14] drm/xe/display: Abstract read/write functions for GGTT PTEs Maarten Lankhorst
2024-09-27 14:13 ` [PATCH 09/14] drm/xe: Make xe_ggtt_pt_ops private Maarten Lankhorst
2024-09-27 14:14 ` [PATCH 10/14] drm/xe/display: Stop dereferencing ggtt in xe_fb_pin Maarten Lankhorst
2024-09-27 14:14 ` [PATCH 11/14] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2024-09-27 14:14 ` [PATCH 12/14] drm/xe/display: Use async flip for flipping initial fb Maarten Lankhorst
2024-09-27 15:14   ` Ville Syrjälä [this message]
2024-09-27 14:14 ` [PATCH 13/14] drm/xe: Move interrupt initialisation until after xe_display_init_noaccel Maarten Lankhorst
2024-09-27 14:14 ` [PATCH 14/14] drm/xe: Initialise GGTT later Maarten Lankhorst
2024-09-27 14:42 ` ✓ CI.Patch_applied: success for drm/xe: Fix flickering when inheriting BIOS fb Patchwork
2024-09-27 14:43 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-27 14:44 ` ✓ CI.KUnit: success " Patchwork
2024-09-27 14:55 ` ✓ CI.Build: " Patchwork
2024-09-27 14:58 ` ✗ CI.Hooks: failure " Patchwork
2024-09-27 14:59 ` ✓ CI.checksparse: success " Patchwork
2024-09-27 15:41 ` ✗ CI.BAT: failure " Patchwork
2024-09-28 10:30 ` ✗ CI.FULL: " 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=ZvbL0GUZ3c5-07qJ@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.