From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/i915: rip out intel_disable_pch_ports
Date: Thu, 13 Sep 2012 13:37:52 -0700 [thread overview]
Message-ID: <20120913133752.35ab1d63@jbarnes-desktop> (raw)
In-Reply-To: <1346962115-7267-2-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 6 Sep 2012 22:08:32 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Even with the old crtc helper code we should have disabled all
> encoders on that pipe by now, and with the new code this would
> definitely paper over a bug. We already have the necessary checks
> in place in intel_disable_transcoder, so if we accidentally leave
> a pch port on, this will be caught.
>
> Hence just rip this all out.
>
> Note that up to the patch in this giant modeset series that removes
> the LVDS special case to avoid disabling LVDS in the encoder->prepare
> callback ("drm/i915/lvds: ditch ->prepare special case"), this was not
> the case for all outputs.
>
> Also note that in
>
> commit 1b3c7a47f993bf9ab6c4c7cc3bbf5588052b58f4
> Author: Zhenyu Wang <zhenyuw@linux.intel.com>
> Date: Wed Nov 25 13:09:38 2009 +0800
>
> drm/i915: Fix LVDS stability issue on Ironlake
>
> this was already discovered independently and worked around. How I
> bloody hate this entire mess of cludges piled on top of other cludges.
Yes this was always an ugly layering violation too. I think I was
worried about a mode set on one crtc getting stale config bits from
another that hadn't been touched...
Anyway now we've fixed it properly.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-09-13 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 20:08 [PATCH 0/4] some follow-up fixlets from the modeset rework Daniel Vetter
2012-09-06 20:08 ` [PATCH 1/4] drm/i915: rip out intel_disable_pch_ports Daniel Vetter
2012-09-13 20:37 ` Jesse Barnes [this message]
2012-09-06 20:08 ` [PATCH 2/4] drm/i915: don't disable fdi links harder in ilk_crtc_enable Daniel Vetter
2012-09-13 20:38 ` Jesse Barnes
2012-09-06 20:08 ` [PATCH 3/4] drm/i915: don't call dpms funcs after set_mode Daniel Vetter
2012-09-13 20:41 ` Jesse Barnes
2012-09-06 20:08 ` [PATCH 4/4] drm/i915: update dpms property in set_mode Daniel Vetter
2012-09-13 20:42 ` Jesse Barnes
2012-09-14 21:38 ` Daniel Vetter
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=20120913133752.35ab1d63@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel.vetter@ffwll.ch \
--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