From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Remove a very stale FIXME
Date: Mon, 10 Dec 2018 21:34:52 +0200 [thread overview]
Message-ID: <20181210193452.GL9144@intel.com> (raw)
In-Reply-To: <20181206170944.16539-2-matthew.d.roper@intel.com>
On Thu, Dec 06, 2018 at 09:09:42AM -0800, Matt Roper wrote:
> SKL watermark calculations can and do trigger atomic transaction
> rejection if no valid set of watermarks can be found. This FIXME
> comment in the code hasn't been relevant for a very long time.
Identical patch already pushed.
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pm.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index a26b4eddda25..9500bda64f26 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -5548,10 +5548,6 @@ skl_compute_wm(struct drm_atomic_state *state)
> * Note that the DDB allocation above may have added more CRTC's that
> * weren't otherwise being modified (and set bits in dirty_pipes) if
> * pipe allocations had to change.
> - *
> - * FIXME: Now that we're doing this in the atomic check phase, we
> - * should allow skl_update_pipe_wm() to return failure in cases where
> - * no suitable watermark values can be found.
> */
> for_each_new_crtc_in_state(state, crtc, cstate, i) {
> struct intel_crtc_state *intel_cstate =
> --
> 2.14.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-10 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 17:09 [PATCH 0/3] New DDB allocation algorithm Matt Roper
2018-12-06 17:09 ` [PATCH 1/3] drm/i915: Remove a very stale FIXME Matt Roper
2018-12-10 19:34 ` Ville Syrjälä [this message]
2018-12-06 17:09 ` [PATCH 2/3] drm/i915: Don't use DDB allocation when choosing gen9 watermark method Matt Roper
2018-12-06 17:09 ` [PATCH 3/3] drm/i915: Switch to level-based DDB allocation algorithm Matt Roper
2018-12-06 23:55 ` [PATCH 3/3] drm/i915: Switch to level-based DDB allocation algorithm (v2) Matt Roper
2018-12-10 20:16 ` Ville Syrjälä
2018-12-06 17:18 ` ✗ Fi.CI.CHECKPATCH: warning for New DDB allocation algorithm Patchwork
2018-12-06 17:19 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-06 17:44 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-12-07 0:23 ` ✗ Fi.CI.SPARSE: warning for New DDB allocation algorithm (rev2) Patchwork
2018-12-07 0:40 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-07 13:44 ` ✓ Fi.CI.IGT: " Patchwork
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=20181210193452.GL9144@intel.com \
--to=ville.syrjala@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