From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Paulo Zanoni" <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: fix assert_cursor on BDW
Date: Fri, 28 Feb 2014 16:10:37 +0200 [thread overview]
Message-ID: <878usvqqea.fsf@intel.com> (raw)
In-Reply-To: <20140227194718.GM3852@intel.com>
On Thu, 27 Feb 2014, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Feb 27, 2014 at 04:30:56PM -0300, Paulo Zanoni wrote:
>> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>>
>> We need to read the correct register, not a register that doesn't exist
>> and will trigger "Unclaimed register" messages when we touch it.
>>
>> Also rearrange the checks in an attempt to prevent this error from
>> happening again.
>>
>> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Pushed to -fixes, thanks for the patch and review.
BR,
Jani.
>
> I was thinking you might want to rearrange intel_crtc_update_cursor()
> the same way, but maybe it's not worth the effort. We may soon have
> to take a look at using the pipe_offsets[] stuff for cursors anyway.
>
>> ---
>> drivers/gpu/drm/i915/intel_display.c | 9 +++++----
>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> This patch is untested, but the "Uncalimed register" message is real, as long as
>> we have the patch to print them.
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index f19e6ea..2e05d1e 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -1095,12 +1095,13 @@ static void assert_cursor(struct drm_i915_private *dev_priv,
>> struct drm_device *dev = dev_priv->dev;
>> bool cur_state;
>>
>> - if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev))
>> - cur_state = I915_READ(CURCNTR_IVB(pipe)) & CURSOR_MODE;
>> - else if (IS_845G(dev) || IS_I865G(dev))
>> +
>> + if (IS_845G(dev) || IS_I865G(dev))
>> cur_state = I915_READ(_CURACNTR) & CURSOR_ENABLE;
>> - else
>> + else if (INTEL_INFO(dev)->gen <= 6 || IS_VALLEYVIEW(dev))
>> cur_state = I915_READ(CURCNTR(pipe)) & CURSOR_MODE;
>> + else
>> + cur_state = I915_READ(CURCNTR_IVB(pipe)) & CURSOR_MODE;
>>
>> WARN(cur_state != state,
>> "cursor on pipe %c assertion failure (expected %s, current %s)\n",
>> --
>> 1.8.5.3
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-02-28 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 19:30 [PATCH] drm/i915: fix assert_cursor on BDW Paulo Zanoni
2014-02-27 19:47 ` Ville Syrjälä
2014-02-28 14:10 ` Jani Nikula [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=878usvqqea.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.com \
--cc=ville.syrjala@linux.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