From: Matt Roper <matthew.d.roper@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Wait until after wm optimization to drop runtime PM reference
Date: Mon, 7 Mar 2016 08:10:00 -0800 [thread overview]
Message-ID: <20160307161000.GA6264@intel.com> (raw)
In-Reply-To: <1457141105.30817.34.camel@intel.com>
On Sat, Mar 05, 2016 at 03:25:05AM +0200, Imre Deak wrote:
> Hi Matt,
>
> On Fri, 2016-03-04 at 15:59 -0800, Matt Roper wrote:
> > At the end of an atomic commit, we currently wait for vblanks to
> > complete, call put() on the various runtime PM references, and then
> > try
> > to optimize our watermarks (on platforms that need two-step watermark
> > programming). This can lead to watermark registers being programmed
> > while the power well is powered down. We need to wait until after
> > watermark optimization is complete before dropping our runtime power
> > references.
> >
> > Note that in the future the watermark optimization is probably going
> > to
> > move to an asynchronous workqueue task that happens at some arbitrary
> > point after vblank. When we make that change, we'll no longer
> > necessarily be operating under the power reference held here, so
> > we'll
> > need to wrap the watermark register programmin in a call to
> > intel_runtime_pm_get_if_in_use() or similar.
> >
> > Cc: arun.siluvery@linux.intel.com
> > Cc: ville.syrjala@linux.intel.com
> > Cc: maarten.lankhorst@linux.intel.com
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94349
> > Fixes: ed4a6a7ca853 ("drm/i915: Add two-stage ILK-style watermark
> > programming (v11)")
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c
> > b/drivers/gpu/drm/i915/intel_display.c
> > index 62d36a7..0af08d7 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -13789,16 +13789,6 @@ static int intel_atomic_commit(struct
> > drm_device *dev,
> > if (!state->legacy_cursor_update)
> > intel_atomic_wait_for_vblanks(dev, dev_priv,
> > crtc_vblank_mask);
> >
> > - for_each_crtc_in_state(state, crtc, crtc_state, i) {
> > - intel_post_plane_update(to_intel_crtc(crtc));
> > -
> > - if (put_domains[i])
> > - modeset_put_power_domains(dev_priv,
> > put_domains[i]);
> > - }
> > -
> > - if (intel_state->modeset)
> > - intel_display_power_put(dev_priv,
> > POWER_DOMAIN_MODESET);
> > -
> > /*
> > * Now that the vblank has passed, we can go ahead and
> > program the
> > * optimal watermarks on platforms that need two-step
> > watermark
> > @@ -13813,6 +13803,16 @@ static int intel_atomic_commit(struct
> > drm_device *dev,
> > dev_priv-
> > >display.optimize_watermarks(intel_cstate);
> > }
> >
> > + for_each_crtc_in_state(state, crtc, crtc_state, i) {
> > + intel_post_plane_update(to_intel_crtc(crtc));
> > +
> > + if (put_domains[i])
> > + modeset_put_power_domains(dev_priv,
> > put_domains[i]);
> > + }
> > +
> > + if (intel_state->modeset)
> > +> intel_display_power_put(dev_priv, POWER_DOMAIN_MODESET);
> > +
>
> Since the error was caused by writing some WM register while the HW is
> suspended, I don't see what would be the point of programming it if the
> register loses its value anyway after dropping the power reference.
> What would make sense to me is to avoid programming the WM registers if
> all the outputs are disabled (like they were when the bug triggered)
> and program them next time around when any output gets enabled.
Yeah, that was actually the first approach I went with:
https://patchwork.freedesktop.org/patch/75772/
Ville felt like it was more of a workaround than a fix though, so I
posted this alternative instead.
Matt
>
> --Imre
>
>
> > mutex_lock(&dev->struct_mutex);
> > drm_atomic_helper_cleanup_planes(dev, state);
> > mutex_unlock(&dev->struct_mutex);
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-07 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 23:59 [PATCH] drm/i915: Wait until after wm optimization to drop runtime PM reference Matt Roper
2016-03-05 1:25 ` Imre Deak
2016-03-07 16:10 ` Matt Roper [this message]
2016-03-07 16:28 ` Imre Deak
2016-03-07 11:47 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-03-08 17:26 ` Matt Roper
2016-03-22 12:55 ` Imre Deak
2016-03-22 13:51 ` Jani Nikula
2016-03-22 14:17 ` Imre Deak
2016-03-22 15:56 ` Matt Roper
2016-03-22 16:25 ` Imre Deak
2016-03-22 16:31 ` Jani Nikula
2016-03-23 8:38 ` Daniel Vetter
2016-03-07 11:53 ` [PATCH] " Maarten Lankhorst
2016-03-07 16:26 ` Matt Roper
2016-03-22 11:04 ` Ville Syrjälä
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=20160307161000.GA6264@intel.com \
--to=matthew.d.roper@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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).