public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org, paulo.r.zanoni@intel.com
Subject: Re: [PATCH 1/6] drm/i915/skl: Make gen8_irq_power_well_post_enable() take a pipe mask
Date: Mon, 9 Mar 2015 09:50:20 +0100	[thread overview]
Message-ID: <20150309085020.GH24485@phenom.ffwll.local> (raw)
In-Reply-To: <1425667853-5717-2-git-send-email-damien.lespiau@intel.com>

On Fri, Mar 06, 2015 at 06:50:48PM +0000, Damien Lespiau wrote:
> While we only need to restore pipe B/C interrupt registers on BDW when
> enabling the power well, skylake a bit more flexible and we'll also need
> to restore the pipe A registers as it has its own power well that can be
> toggled.
> 
> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_irq.c         | 15 ++++++++++-----
>  drivers/gpu/drm/i915/intel_drv.h        |  3 ++-
>  drivers/gpu/drm/i915/intel_runtime_pm.c |  3 ++-
>  3 files changed, 14 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 9baecb7..d77a4b6 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -3169,15 +3169,20 @@ static void gen8_irq_reset(struct drm_device *dev)
>  	ibx_irq_reset(dev);
>  }
>  
> -void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv)
> +void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,
> +				     unsigned int pipe_mask)
>  {
>  	uint32_t extra_ier = GEN8_PIPE_VBLANK | GEN8_PIPE_FIFO_UNDERRUN;
>  
>  	spin_lock_irq(&dev_priv->irq_lock);
> -	GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_B, dev_priv->de_irq_mask[PIPE_B],
> -			  ~dev_priv->de_irq_mask[PIPE_B] | extra_ier);
> -	GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_C, dev_priv->de_irq_mask[PIPE_C],
> -			  ~dev_priv->de_irq_mask[PIPE_C] | extra_ier);
> +	if (pipe_mask & 1 << PIPE_B)
> +		GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_B,
> +				  dev_priv->de_irq_mask[PIPE_B],
> +				  ~dev_priv->de_irq_mask[PIPE_B] | extra_ier);
> +	if (pipe_mask & 1 << PIPE_C)
> +		GEN8_IRQ_INIT_NDX(DE_PIPE, PIPE_C,
> +				  dev_priv->de_irq_mask[PIPE_C],
> +				  ~dev_priv->de_irq_mask[PIPE_C] | extra_ier);
>  	spin_unlock_irq(&dev_priv->irq_lock);

Since this now takes a pipe mask I really think we should eventually move
this as a call into the gen8+ crtc enable code ...
-Daniel

>  }
>  
> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> index ff79dca..c77128c 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -840,7 +840,8 @@ static inline bool intel_irqs_enabled(struct drm_i915_private *dev_priv)
>  }
>  
>  int intel_get_crtc_scanline(struct intel_crtc *crtc);
> -void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv);
> +void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,
> +				     unsigned int pipe_mask);
>  
>  /* intel_crt.c */
>  void intel_crt_init(struct drm_device *dev);
> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c b/drivers/gpu/drm/i915/intel_runtime_pm.c
> index 6d8e29a..35e0cb6 100644
> --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
> @@ -195,7 +195,8 @@ static void hsw_power_well_post_enable(struct drm_i915_private *dev_priv)
>  	vga_put(dev->pdev, VGA_RSRC_LEGACY_IO);
>  
>  	if (IS_BROADWELL(dev) || (INTEL_INFO(dev)->gen >= 9))
> -		gen8_irq_power_well_post_enable(dev_priv);
> +		gen8_irq_power_well_post_enable(dev_priv,
> +						1 << PIPE_C | 1 << PIPE_B);
>  }
>  
>  static void hsw_set_power_well(struct drm_i915_private *dev_priv,
> -- 
> 1.8.3.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-09  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 18:50 [PATCH 0/6] SKL post-enable power well hook (v2) Damien Lespiau
2015-03-06 18:50 ` [PATCH 1/6] drm/i915/skl: Make gen8_irq_power_well_post_enable() take a pipe mask Damien Lespiau
2015-03-09  8:50   ` Daniel Vetter [this message]
2015-03-06 18:50 ` [PATCH 2/6] drm/i915/skl: Introduce enable_requested and is_enabled in the power well code Damien Lespiau
2015-03-06 18:50 ` [PATCH 3/6] drm/i915/skl: Mirror what we do on HSW for the power well enable log message Damien Lespiau
2015-03-06 18:50 ` [PATCH 4/6] drm/i915/skl: Restore pipe interrupt registers after power well enabling Damien Lespiau
2015-03-06 18:50 ` [PATCH 5/6] drm/i915: Remove unused condition in hsw_power_well_post_enable() Damien Lespiau
2015-03-06 18:50 ` [PATCH 6/6] drm/i915/skl: Restore the DDI translation tables when enabling PW1 Damien Lespiau
2015-03-07  1:32   ` shuang.he
2015-03-06 19:28 ` [PATCH 0/6] SKL post-enable power well hook (v2) Paulo Zanoni
2015-03-09  9:00   ` Daniel Vetter

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=20150309085020.GH24485@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@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