All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/display: Add block_dc6_needed variable into intel_crtc
Date: Fri, 13 Sep 2024 18:03:47 +0300	[thread overview]
Message-ID: <ZuRUU5JCu4LMoy--@intel.com> (raw)
In-Reply-To: <20240913073347.3273589-2-jouni.hogander@intel.com>

On Fri, Sep 13, 2024 at 10:33:46AM +0300, Jouni Högander wrote:
> We need to block DC6 entry in case of Panel Replay as enabling VBI doesn't
> prevent DC6 in case of Panel Replay. This causes problems if user-space is
> polling for vblank events. For this purpose add new block_dc6_needed
> variable into intel_crtc.
> 
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
>  .../gpu/drm/i915/display/intel_display_irq.c  | 28 +++++++++++++++++++
>  .../gpu/drm/i915/display/intel_display_irq.h  |  3 ++
>  .../drm/i915/display/intel_display_types.h    |  7 +++++
>  drivers/gpu/drm/i915/display/intel_psr.c      |  7 +++++
>  4 files changed, 45 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.c b/drivers/gpu/drm/i915/display/intel_display_irq.c
> index 8f13f148c73e3..7ff721bcec0d3 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_irq.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_irq.c
> @@ -1361,6 +1361,34 @@ static bool gen11_dsi_configure_te(struct intel_crtc *intel_crtc,
>  	return true;
>  }
>  
> +/**
> + * block_dc6_on_vblank_get - get block DC6 entry reference
> + *
> + * @_crtc: drm crtc pointer
> + *
> + * This function is called from Panel Replay code when Panel Replay gets
> + * activated. Intention is to block DC6 entry when VBI is enabled and Panel
> + * Replay is active.
> + */
> +void block_dc6_on_vblank_get(struct drm_crtc *_crtc)
> +{
> +	to_intel_crtc(_crtc)->block_dc6_needed++;
> +}
> +
> +/**
> + * block_dc6_on_vblank_put - free block DC6 entry reference
> + *
> + * @crtc: drm crtc pointer
> + *
> + * This function is called from Panel Replay code when Panel Replay is
> + * deactivated. Intention is to block DC6 entry when VBI is enabled and Panel
> + * Replay is active.
> + */
> +void block_dc6_on_vblank_put(struct drm_crtc *crtc)
> +{
> +	to_intel_crtc(crtc)->block_dc6_needed--;
> +}
> +
>  int bdw_enable_vblank(struct drm_crtc *_crtc)
>  {
>  	struct intel_crtc *crtc = to_intel_crtc(_crtc);
> diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.h b/drivers/gpu/drm/i915/display/intel_display_irq.h
> index 2a090dd6abd7c..fe3ada8f37283 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_irq.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_irq.h
> @@ -77,6 +77,9 @@ void i965_pipestat_irq_handler(struct drm_i915_private *i915, u32 iir, u32 pipe_
>  void valleyview_pipestat_irq_handler(struct drm_i915_private *i915, u32 pipe_stats[I915_MAX_PIPES]);
>  void i8xx_pipestat_irq_handler(struct drm_i915_private *i915, u16 iir, u32 pipe_stats[I915_MAX_PIPES]);
>  
> +void block_dc6_on_vblank_get(struct drm_crtc *crtc);
> +void block_dc6_on_vblank_put(struct drm_crtc *crtc);
> +
>  void intel_display_irq_init(struct drm_i915_private *i915);
>  
>  #endif /* __INTEL_DISPLAY_IRQ_H__ */
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 000ab373c8879..df0c3eb750809 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1413,6 +1413,13 @@ struct intel_crtc {
>  #ifdef CONFIG_DEBUG_FS
>  	struct intel_pipe_crc pipe_crc;
>  #endif
> +
> +	/*
> +	 * We need to block DC6 entry in case of Panel Replay as enabling VBI doesn't
> +	 * prevent DC6 in case of Panel Replay. This causes problems if user-space is
> +	 * polling for vblank events.
> +	 */
> +	u8 block_dc6_needed;
>  };
>  
>  struct intel_plane {
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 1a4ef231a53ca..f9e5177893c46 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -35,6 +35,7 @@
>  #include "intel_cursor_regs.h"
>  #include "intel_ddi.h"
>  #include "intel_de.h"
> +#include "intel_display_irq.h"
>  #include "intel_display_types.h"
>  #include "intel_dp.h"
>  #include "intel_dp_aux.h"
> @@ -970,6 +971,9 @@ static void dg2_activate_panel_replay(struct intel_dp *intel_dp)
>  			       val);
>  	}
>  
> +	if (intel_dp_is_edp(intel_dp))
> +		block_dc6_on_vblank_get(&intel_crtc_for_pipe(display, intel_dp->psr.pipe)->base);

This still feels racy. Can't we make it just a simple flag that
gets set just once before/during intel_crtc_vblank_on()?

> +
>  	intel_de_rmw(display,
>  		     PSR2_MAN_TRK_CTL(display, intel_dp->psr.transcoder),
>  		     0, ADLP_PSR2_MAN_TRK_CTL_SF_CONTINUOS_FULL_FRAME);
> @@ -2005,6 +2009,9 @@ static void intel_psr_exit(struct intel_dp *intel_dp)
>  	}
>  
>  	if (intel_dp->psr.panel_replay_enabled) {
> +		if (intel_dp_is_edp(intel_dp))
> +			block_dc6_on_vblank_put(drm_crtc_from_index(display->drm,
> +								    intel_dp->psr.pipe));
>  		intel_de_rmw(display, TRANS_DP2_CTL(intel_dp->psr.transcoder),
>  			     TRANS_DP2_PANEL_REPLAY_ENABLE, 0);
>  	} else if (intel_dp->psr.sel_update_enabled) {
> -- 
> 2.34.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-09-13 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  7:33 [PATCH 0/2] Block DC6 on Vblank enable for Panel Replay Jouni Högander
2024-09-13  7:33 ` [PATCH 1/2] drm/i915/display: Add block_dc6_needed variable into intel_crtc Jouni Högander
2024-09-13 15:03   ` Ville Syrjälä [this message]
2024-09-14  1:33   ` kernel test robot
2024-09-14  2:55   ` kernel test robot
2024-09-13  7:33 ` [PATCH 2/2] drm/i915/display: Prevent DC6 while vblank is enabled for Panel Replay Jouni Högander
2024-09-13 14:52 ` ✗ Fi.CI.SPARSE: warning for Block DC6 on Vblank enable " Patchwork
2024-09-13 14:52 ` ✗ Fi.CI.DOCS: " Patchwork
2024-09-13 15:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-14 23:04 ` ✗ Fi.CI.IGT: 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=ZuRUU5JCu4LMoy--@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jouni.hogander@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.