From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Wessel <jason.wessel@windriver.com>,
Jason@freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [BISECTED, -next] drm/i915: blurred HDMI output
Date: Mon, 18 Oct 2010 14:05:05 -0700 [thread overview]
Message-ID: <20101018140505.44b04a09@jbarnes-desktop> (raw)
In-Reply-To: <201010182237.44267.arnd@arndb.de>
On Mon, 18 Oct 2010 22:37:43 +0200
Arnd Bergmann <arnd@arndb.de> wrote:
> On Monday 18 October 2010 22:30:17 Arnd Bergmann wrote:
>
> > I don't think the code path you patch here actually gets used, since
> > intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
>
> FWIW, the patch below does work.
>
> Arnd
>
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5311,6 +5311,9 @@ static void intel_setup_outputs(struct drm_device *dev)
> if (IS_MOBILE(dev) && !IS_I830(dev))
> intel_lvds_init(dev);
>
> + I915_WRITE(PFIT_CONTROL, 0);
> + I915_WRITE(LVDS, 0);
> +
> if (HAS_PCH_SPLIT(dev)) {
> dpd_is_edp = intel_dpd_is_edp(dev);
Oh of course, I was thinking the output functions did detection, but we
short circuit it before that.
So we should probably do it in setup_outputs or init_display once we've
figured out there's no LVDS. It's cool that the panel fitter still has
an effect even on non-LVDS platforms though, maybe we really should
treat it as a part of the CRTC rather than the LVDS encoder after all.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-10-18 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 17:37 [BISECTED, -next] drm/i915: blurred HDMI output Arnd Bergmann
2010-10-18 18:56 ` Jesse Barnes
2010-10-18 19:13 ` Arnd Bergmann
2010-10-18 19:28 ` Jesse Barnes
2010-10-18 19:57 ` Arnd Bergmann
2010-10-18 20:15 ` Jesse Barnes
2010-10-18 20:30 ` Arnd Bergmann
2010-10-18 20:37 ` Arnd Bergmann
2010-10-18 21:05 ` Jesse Barnes [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=20101018140505.44b04a09@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Jason@freedesktop.org \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason.wessel@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.