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 at intel.com>
For this patch.
Eugeni
