On Wed, 14 Jan 2015, Ander Conselvan de Oliveira <conselvan2@xxxxxxxxx> wrote: > On 01/14/2015 12:47 PM, Jani Nikula wrote: >> On Tue, 13 Jan 2015, Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@xxxxxxxxx> wrote: >>> If QUIRK_PIPEA_FORCE is necessary, intel_sanitize_crtc() might trigger >>> a mode set. In that case, if pipe A is disabled and pipe B is mapped to >>> plane B, that mode set happens before the mapping is fixed. Due to the >>> wrong state, the call to disable pipe B disables plane A (which is >>> already disabled) and later an assertion for plane B being enabled >>> (while it should have been disabled) is triggered. >>> >>> References: https://bugs.freedesktop.org/show_bug.cgi?id=72782 >> >> If the patch is expected to fix the bug, please use Bugzilla:. If you're >> referencing a bug because it's otherwise relevant, please use >> References:. >> >> Which one is this? > > This showed up in the dmesg attached to the referenced bug, but is not > the root cause of the reported problem. As far as I know, there is no > open bug for this particular issue. Ah, so it's correct as it is. Sorry for the noise. Please carry on. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
