From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, 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 12:53:38 +0100 [thread overview]
Message-ID: <56DD6BC2.4060609@linux.intel.com> (raw)
In-Reply-To: <1457135979-23727-1-git-send-email-matthew.d.roper@intel.com>
Op 05-03-16 om 00:59 schreef Matt Roper:
> 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>
post_plane_update can call intel_update_watermarks, will this cause any unintended behavioral changes
if intel_update_watermarks is called before optimize_watermarks?
~Maarten
_______________________________________________
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 11:53 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
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 ` Maarten Lankhorst [this message]
2016-03-07 16:26 ` [PATCH] " 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=56DD6BC2.4060609@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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).