From: Daniel Vetter <daniel@ffwll.ch>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: No panel fitter on 830M or non-mobile gen2/3 platforms
Date: Fri, 10 Jan 2014 18:02:59 +0100 [thread overview]
Message-ID: <20140110170259.GE4770@phenom.ffwll.local> (raw)
In-Reply-To: <1389355607-8794-2-git-send-email-ville.syrjala@linux.intel.com>
On Fri, Jan 10, 2014 at 02:06:45PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> PFIT_CONTROL doesn't exist on 830M, so avoid reading it in
> i9xx_get_pfit_config().
>
> Also assume that only mobile gen2/3 chipsets have a panel fitter. This
> matches the documentation, but I didn't have real hardware to verify.
>
> Gen4 docmentation is a bit inconsistent, but experimenetation on my
> LPT machine suggests that the panel fitter is available on non-mobile
> gen4 platforms. At least on this machine panel fitter appears works
> just fine even on VGA output.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 3 +++
> drivers/gpu/drm/i915/intel_overlay.c | 2 +-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index a51e105..9f8c5b5 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5428,6 +5428,9 @@ static void i9xx_get_pfit_config(struct intel_crtc *crtc,
> struct drm_i915_private *dev_priv = dev->dev_private;
> uint32_t tmp;
>
> + if (INTEL_INFO(dev)->gen <= 3 && (IS_I830(dev) || !IS_MOBILE(dev)))
> + return;
> +
> tmp = I915_READ(PFIT_CONTROL);
> if (!(tmp & PFIT_ENABLE))
> return;
> diff --git a/drivers/gpu/drm/i915/intel_overlay.c b/drivers/gpu/drm/i915/intel_overlay.c
> index a1397b1..424f094 100644
> --- a/drivers/gpu/drm/i915/intel_overlay.c
> +++ b/drivers/gpu/drm/i915/intel_overlay.c
> @@ -1005,7 +1005,7 @@ static int intel_panel_fitter_pipe(struct drm_device *dev)
> u32 pfit_control;
>
> /* i830 doesn't have a panel fitter */
> - if (IS_I830(dev))
> + if (INTEL_INFO(dev)->gen <= 3 && (IS_I830(dev) || !IS_MOBILE(dev)))
Hm, we could switch that code to the pipe config. Like we've already done
for the double-wide stuff. Like we've done for the double-wide checks
already ...
-Daniel
> return -1;
>
> pfit_control = I915_READ(PFIT_CONTROL);
> --
> 1.8.3.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-01-10 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 12:06 [PATCH 0/3] drm/i915: A few small fixes for older platforms ville.syrjala
2014-01-10 12:06 ` [PATCH 1/3] drm/i915: No panel fitter on 830M or non-mobile gen2/3 platforms ville.syrjala
2014-01-10 17:02 ` Daniel Vetter [this message]
2014-01-10 12:06 ` [PATCH 2/3] drm/i915: 830M doesn't have an LVDS port ville.syrjala
2014-01-10 12:06 ` [PATCH 3/3] drm/i915: Fix 915GM self-refresh enable/disable ville.syrjala
2014-01-10 14:23 ` [PATCH 0/3] drm/i915: A few small fixes for older platforms Chris Wilson
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=20140110170259.GE4770@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox