From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/display: Restore dsparb_lock.
Date: Wed, 29 Mar 2023 15:32:55 -0400 [thread overview]
Message-ID: <ZCSSZyYqplVSR8T9@intel.com> (raw)
In-Reply-To: <87tty44zi7.fsf@intel.com>
On Tue, Mar 28, 2023 at 07:22:24PM +0300, Jani Nikula wrote:
> On Mon, 27 Mar 2023, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > uncore->lock only protects the forcewake domain itself,
> > not the register accesses.
> >
> > uncore's _fw alternatives are for cases where the domains
> > are not needed because we are sure that they are already
> > awake.
> >
> > So the move towards the uncore's _fw alternatives seems
> > right, however using the uncore-lock to protect the dsparb
> > registers seems an abuse of the uncore-lock.
> >
> > Let's restore the previous individual lock and try to get
> > rid of the direct uncore accesses from the display code.
> >
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Link: https://patchwork.freedesktop.org/patch/msgid/20230308165859.235520-1-rodrigo.vivi@intel.com
> > ---
> > drivers/gpu/drm/i915/display/i9xx_wm.c | 13 ++-----------
> > drivers/gpu/drm/i915/display/intel_display_core.h | 3 +++
> > drivers/gpu/drm/i915/i915_driver.c | 1 +
> > 3 files changed, 6 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/i9xx_wm.c b/drivers/gpu/drm/i915/display/i9xx_wm.c
> > index caef72d38798..8fe0b5c63d3a 100644
> > --- a/drivers/gpu/drm/i915/display/i9xx_wm.c
> > +++ b/drivers/gpu/drm/i915/display/i9xx_wm.c
> > @@ -1771,16 +1771,7 @@ static void vlv_atomic_update_fifo(struct intel_atomic_state *state,
> >
> > trace_vlv_fifo_size(crtc, sprite0_start, sprite1_start, fifo_size);
> >
> > - /*
> > - * uncore.lock serves a double purpose here. It allows us to
> > - * use the less expensive I915_{READ,WRITE}_FW() functions, and
> > - * it protects the DSPARB registers from getting clobbered by
> > - * parallel updates from multiple pipes.
> > - *
> > - * intel_pipe_update_start() has already disabled interrupts
> > - * for us, so a plain spin_lock() is sufficient here.
> > - */
> > - spin_lock(&uncore->lock);
> > + spin_lock(&dev_priv->display.wm.dsparb_lock);
> >
> > switch (crtc->pipe) {
> > case PIPE_A:
> > @@ -1840,7 +1831,7 @@ static void vlv_atomic_update_fifo(struct intel_atomic_state *state,
> >
> > intel_uncore_posting_read_fw(uncore, DSPARB);
> >
> > - spin_unlock(&uncore->lock);
> > + spin_unlock(&dev_priv->display.wm.dsparb_lock);
> > }
> >
> > #undef VLV_FIFO
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
> > index 0b5509f268a7..e4da8902c878 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_core.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
> > @@ -264,6 +264,9 @@ struct intel_wm {
> > */
> > struct mutex wm_mutex;
> >
> > + /* protects DSPARB registers on pre-g4x/vlv/chv */
> > + spinlock_t dsparb_lock;
> > +
> > bool ipc_enabled;
> > };
> >
> > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > index 12b5296ee744..e90a0c0403a6 100644
> > --- a/drivers/gpu/drm/i915/i915_driver.c
> > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > @@ -223,6 +223,7 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
> > mutex_init(&dev_priv->display.pps.mutex);
> > mutex_init(&dev_priv->display.hdcp.comp_mutex);
> > spin_lock_init(&dev_priv->display.dkl.phy_lock);
> > + spin_lock_init(&dev_priv->display.wm.dsparb_lock);
>
> Can we do this in i9xx_wm_init() instead?
I was going to modify it here right now, but then I noticed
the cases above and remembered why I have put it here.
All the display locks are getting set in here.
Probably better to move with this patch as is and then add
a new on top moving the various locks to its individual inits?
>
>
> >
> > i915_memcpy_init_early(dev_priv);
> > intel_runtime_pm_init_early(&dev_priv->runtime_pm);
>
> --
> Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-29 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 16:12 [Intel-gfx] [PATCH 1/2] drm/i915/display: Restore dsparb_lock Rodrigo Vivi
2023-03-27 16:12 ` [Intel-gfx] [PATCH 2/2] drm/i915/i9xx_wm: Prefer intel_de functions over intel_uncore Rodrigo Vivi
2023-03-27 21:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915/display: Restore dsparb_lock Patchwork
2023-03-27 22:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-28 5:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-03-28 16:22 ` [Intel-gfx] [PATCH 1/2] " Jani Nikula
2023-03-29 19:32 ` Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 16:58 Rodrigo Vivi
2023-03-08 22:03 ` Ville Syrjälä
2023-03-09 22:03 ` Rodrigo Vivi
2023-03-10 16:26 ` Ville Syrjälä
2023-03-10 19:09 ` Rodrigo Vivi
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=ZCSSZyYqplVSR8T9@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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.