intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 03/10] drm/i915: fix intel_init_power_wells
Date: Tue, 22 Jan 2013 15:47:27 +0200	[thread overview]
Message-ID: <20130122134727.GF9135@intel.com> (raw)
In-Reply-To: <20130122130226.GJ31870@phenom.ffwll.local>

On Tue, Jan 22, 2013 at 02:02:26PM +0100, Daniel Vetter wrote:
> On Mon, Jan 21, 2013 at 03:37:42PM +0200, Ville Syrjälä wrote:
> > On Fri, Jan 18, 2013 at 06:29:05PM -0200, Paulo Zanoni wrote:
> > > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > 
> > > The current code was wrong in many different ways, so this is a full
> > > rewrite. We don't have "different power wells for different parts of
> > > the GPU", we have a single power well, but we have multiple registers
> > > that can be used to request enabling/disabling the power well. So
> > > let's be a good citizen and only use the register we're supposed to
> > > use, except when we're loading the driver, where we clear the request
> > > made by the BIOS.
> > > 
> > > If any of the registers is requesting the power well to be enabled, it
> > > will be enabled. If none of the registers is requesting the power well
> > > to be enabled, it will be disabled.
> > > 
> > > For now we're just forcing the power well to be enabled, but in the
> > > next commits we'll change this.
> > > 
> > > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/i915_reg.h      |    8 ++--
> > >  drivers/gpu/drm/i915/intel_display.c |    5 +--
> > >  drivers/gpu/drm/i915/intel_drv.h     |    2 +-
> > >  drivers/gpu/drm/i915/intel_pm.c      |   70 +++++++++++++++++++++++++---------
> > >  4 files changed, 59 insertions(+), 26 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > > index 2521617..f054554 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -4414,10 +4414,10 @@
> > >  #define   AUDIO_CP_READY_C		(1<<9)
> > >  
> > >  /* HSW Power Wells */
> > > -#define HSW_PWR_WELL_CTL1			0x45400 /* BIOS */
> > > -#define HSW_PWR_WELL_CTL2			0x45404 /* Driver */
> > > -#define HSW_PWR_WELL_CTL3			0x45408 /* KVMR */
> > > -#define HSW_PWR_WELL_CTL4			0x4540C /* Debug */
> > > +#define HSW_PWR_WELL_BIOS			0x45400 /* CTL1 */
> > > +#define HSW_PWR_WELL_DRIVER			0x45404 /* CTL2 */
> > > +#define HSW_PWR_WELL_KVMR			0x45408 /* CTL3 */
> > > +#define HSW_PWR_WELL_DEBUG			0x4540C /* CTL4 */
> > >  #define   HSW_PWR_WELL_ENABLE			(1<<31)
> > >  #define   HSW_PWR_WELL_STATE			(1<<30)
> > >  #define HSW_PWR_WELL_CTL5			0x45410
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > index b35902e..4a9f048 100644
> > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > @@ -8647,10 +8647,7 @@ static void i915_disable_vga(struct drm_device *dev)
> > >  
> > >  void intel_modeset_init_hw(struct drm_device *dev)
> > >  {
> > > -	/* We attempt to init the necessary power wells early in the initialization
> > > -	 * time, so the subsystems that expect power to be enabled can work.
> > > -	 */
> > > -	intel_init_power_wells(dev);
> > > +	intel_init_power_well(dev);
> > >  
> > >  	intel_prepare_ddi(dev);
> > >  
> > > diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> > > index aeff0d1..8cfad75 100644
> > > --- a/drivers/gpu/drm/i915/intel_drv.h
> > > +++ b/drivers/gpu/drm/i915/intel_drv.h
> > > @@ -666,7 +666,7 @@ extern void intel_update_fbc(struct drm_device *dev);
> > >  extern void intel_gpu_ips_init(struct drm_i915_private *dev_priv);
> > >  extern void intel_gpu_ips_teardown(void);
> > >  
> > > -extern void intel_init_power_wells(struct drm_device *dev);
> > > +extern void intel_init_power_well(struct drm_device *dev);
> > >  extern void intel_enable_gt_powersave(struct drm_device *dev);
> > >  extern void intel_disable_gt_powersave(struct drm_device *dev);
> > >  extern void gen6_gt_check_fifodbg(struct drm_i915_private *dev_priv);
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > > index 5a8a72c..2273b9c 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -4043,33 +4043,69 @@ void intel_init_clock_gating(struct drm_device *dev)
> > >  	dev_priv->display.init_clock_gating(dev);
> > >  }
> > >  
> > > -/* Starting with Haswell, we have different power wells for
> > > - * different parts of the GPU. This attempts to enable them all.
> > > +static void intel_set_power_well(struct drm_device *dev, bool enable)
> > > +{
> > > +	struct drm_i915_private *dev_priv = dev->dev_private;
> > > +	bool is_enabled, enable_requested;
> > > +	uint32_t tmp;
> > > +
> > > +	tmp = I915_READ(HSW_PWR_WELL_DRIVER);
> > > +	is_enabled = !!(tmp & HSW_PWR_WELL_STATE);
> > > +	enable_requested = !!(tmp & HSW_PWR_WELL_ENABLE);
> > > +
> > > +	if (enable) {
> > > +		if (!enable_requested)
> > > +			I915_WRITE(HSW_PWR_WELL_DRIVER, HSW_PWR_WELL_ENABLE);
> > > +
> > > +		if (!is_enabled) {
> > > +			DRM_DEBUG_KMS("Enabling power well\n");
> > > +			if (wait_for((I915_READ(HSW_PWR_WELL_DRIVER) &
> > > +				      HSW_PWR_WELL_STATE), 20))
> > > +				DRM_ERROR("Timeout enabling power well\n");
> > > +		}
> > > +	} else {
> > > +		if (enable_requested)
> > > +			I915_WRITE(HSW_PWR_WELL_DRIVER, 0);
> > > +
> > > +		if (is_enabled) {
> > > +			if (I915_READ(HSW_PWR_WELL_BIOS) & HSW_PWR_WELL_ENABLE)
> > > +				DRM_DEBUG_KMS("Not disabling power well: requested by BIOS\n");
> > > +			else if (I915_READ(HSW_PWR_WELL_KVMR) & HSW_PWR_WELL_ENABLE)
> > > +				DRM_DEBUG_KMS("Not disabling power well: requested by KVMR\n");
> > > +			else if (I915_READ(HSW_PWR_WELL_DEBUG) & HSW_PWR_WELL_ENABLE)
> > > +				DRM_DEBUG_KMS("Not disabling power well: requested by DEBUG\n");
> > > +			else {
> > > +				DRM_DEBUG_KMS("Disabling power well\n");
> > > +				if (wait_for((I915_READ(HSW_PWR_WELL_DRIVER) &
> > > +					      HSW_PWR_WELL_STATE) == 0, 20))
> > > +					DRM_ERROR("Timeout disabling power well\n");
> > > +			}
> > > +		}
> > > +	}
> > 
> > The documentation says not to touch the enable bits if there's a state
> > transition already in progress. I have no idea how we're supposed to do
> > that without all kinds of race conditions due multiple entities making
> > requests simultaneosly. Do you know something about this that's not in
> > the documentation?
> > 
> > Apart from that the patch looks good to me.
> 
> We should be protected by dev->mode_config.mutex in all callsite (safe for
> maybe setup/resume, but that's just cosmetics). The dev->struct_mutex
> locking we already have seems to be cargo-culting afaict. Paulo, can you
> add a follow-up patch to unconfuse matters here a bit?

I'm not concerned about out driver, but mainly KVMR. It can
enable/disable the power well at any time. Unless of course KVMR is
never used on Linux machines, in which case my worries are pointless.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-01-22 13:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 20:29 [PATCH 00/10] Haswell unclaimed register fixes and power well enabling Paulo Zanoni
2013-01-18 20:29 ` [PATCH 01/10] drm/i915: don't save/restore DSPARB on gen5+ Paulo Zanoni
2013-01-24  9:26   ` Jani Nikula
2013-01-24 15:58     ` Daniel Vetter
2013-01-18 20:29 ` [PATCH 02/10] drm/i915: don't read DP_TP_STATUS(PORT_A) Paulo Zanoni
2013-01-24  9:29   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 03/10] drm/i915: fix intel_init_power_wells Paulo Zanoni
2013-01-21 13:37   ` Ville Syrjälä
2013-01-22 13:02     ` Daniel Vetter
2013-01-22 13:47       ` Ville Syrjälä [this message]
2013-01-22 14:13   ` Ville Syrjälä
2013-01-24 11:39   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 04/10] drm/i915: dynamic Haswell display power well support Paulo Zanoni
2013-01-24 13:15   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 05/10] drm/i915: only disable enabled planes on intel_fb_restore_mode Paulo Zanoni
2013-01-18 20:29 ` [PATCH 06/10] drm/i915: check the power down well on assert_pipe() Paulo Zanoni
2013-01-21 13:45   ` Ville Syrjälä
2013-01-22 13:04     ` Daniel Vetter
2013-01-22 13:49       ` Ville Syrjälä
2013-01-25 15:40     ` Paulo Zanoni
2013-01-25 15:53       ` Ville Syrjälä
2013-01-25 16:04         ` Paulo Zanoni
2013-01-25 16:16           ` Ville Syrjälä
2013-01-18 20:29 ` [PATCH 07/10] drm/i915: turn on the power well before suspending Paulo Zanoni
2013-01-24 13:16   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 08/10] drm/i915: set TRANSCODER_EDP even earlier Paulo Zanoni
2013-01-24 11:59   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 09/10] drm/i915: print IVB/HSW display error interrupts Paulo Zanoni
2013-01-18 21:53   ` Ben Widawsky
2013-01-24 13:06     ` Jani Nikula
2013-01-24 13:04   ` Jani Nikula
2013-01-18 20:29 ` [PATCH 10/10] drm/i915: remove "unclaimed register" checks from I915_WRITE Paulo Zanoni
2013-01-18 20:49   ` Ben Widawsky
2013-01-18 20:56     ` Chris Wilson

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=20130122134727.GF9135@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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;
as well as URLs for NNTP newsgroup(s).