From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Matthew Auld <matthew.auld@intel.com>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time
Date: Tue, 29 Nov 2016 21:36:23 +0200 [thread overview]
Message-ID: <20161129193623.GV31595@intel.com> (raw)
In-Reply-To: <CAM0jSHMV9PcTAtLWHkCNKirg+6cMYZy6pE=numArhteT1XncdA@mail.gmail.com>
On Tue, Nov 29, 2016 at 02:40:45PM +0000, Matthew Auld wrote:
> On 29 November 2016 at 14:13, <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> >
> > Looks like we're only initializing dev_priv->atomic_cdclk_freq
> > at resume and commit times, not at init time. Let's do that as
> > well.
> >
> > We're now hitting the 'WARN_ON(intel_state->cdclk == 0)' in
> > hsw_compute_linetime_wm() on account of populating
> > intel_state->cdclk from dev_priv->atomic_cdclk_freq.
> > Previously we were mispopulating intel_state->cdclk with
> > dev_priv->cdclk_freq which always had a proper value at init
> > time and hence the WARN_ON() didn't trigger.
> >
> > Cc: stable@vger.kernel.org
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Reported-by: Matthew Auld <matthew.auld@intel.com>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98902
> > Fixes: e0ca7a6be38c ("drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things")
> > Signed-off-by: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> Tested-by: Matthew Auld <matthew.auld@intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Pushed to dinq. Thanks for the testing and review.
--
Ville Syrj�l�
Intel OTC
prev parent reply other threads:[~2016-11-29 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 14:13 [PATCH] drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time ville.syrjala
2016-11-29 14:40 ` [Intel-gfx] " Matthew Auld
2016-11-29 19:36 ` Ville Syrjälä [this message]
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=20161129193623.GV31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.william.auld@gmail.com \
--cc=stable@vger.kernel.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).