From: Eugeni Dodonov <eugeni.dodonov@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: drm/i915: Disable DDI Pipe Control on HSW while disabling pipe
Date: Fri, 08 Jun 2012 10:50:00 -0300 [thread overview]
Message-ID: <4FD20308.40700@linux.intel.com> (raw)
In-Reply-To: <20120608124928.GB5761@phenom.ffwll.local>
On 06/08/2012 09:49 AM, Daniel Vetter wrote:
> On Fri, Jun 08, 2012 at 11:44:23AM +0530, Shobhit Kumar wrote:
>> In Haswell while disabling a pipe, we need to disable the DDI control as
>> well along with the PIPECONF. Otherwise we will hit assertions during crtc
>> disable
>
> Hm, can you add such an example assert with backtrace please? All these
> asserts encode our current understanding of the hw depency chain, so I'd
> like to check whether we're really doing the right thing and don't just
> stfu some dmesg noise.
>
> Thanks, Daniel
This is part of the pipe disabling process starting with Haswell. DDI
pipe function control should be disabled when pipe is being disabled,
otherwise it stays in enabled state and on next enabling we hit the
assert within assert_fdi_tx:
...
if (IS_HASWELL(dev_priv->dev)) {
/* On Haswell, DDI is used instead of FDI_TX_CTL */
reg = DDI_FUNC_CTL(pipe);
val = I915_READ(reg);
cur_state = !!(val & PIPE_DDI_FUNC_ENABLE);
...
I missed this in the initial enabling and Shobhit has catched this - thanks!
So you can also add:
Reviewed-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
For this patch.
Eugeni
next prev parent reply other threads:[~2012-06-08 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 6:14 drm/i915: Disable DDI Pipe Control on HSW while disabling pipe Shobhit Kumar
2012-06-08 12:49 ` Daniel Vetter
2012-06-08 13:50 ` Eugeni Dodonov [this message]
2012-06-11 5:25 ` Shobhit Kumar
2012-06-11 7:08 ` Daniel Vetter
2012-06-11 8:27 ` Shobhit Kumar
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=4FD20308.40700@linux.intel.com \
--to=eugeni.dodonov@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=eugeni.dodonov@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