From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915: Introduce i9xx_has_pfit()
Date: Tue, 19 Mar 2019 13:24:16 +0000 [thread overview]
Message-ID: <d0c68085-e904-102e-2646-0061043a406c@linux.intel.com> (raw)
In-Reply-To: <20190318165633.28924-2-ville.syrjala@linux.intel.com>
On 18/03/2019 16:56, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Make the code self-documenting by introducing i9xx_has_pfit().
> Also make PNV an exceptional case so that we can unset
> .is_mobile for the desktop variant.
>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 61acbaf2af75..0ddd83dbd768 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -7961,14 +7961,22 @@ static int vlv_crtc_compute_clock(struct intel_crtc *crtc,
> return 0;
> }
>
> +static bool i9xx_has_pfit(struct drm_i915_private *dev_priv)
> +{
> + if (IS_I830(dev_priv))
> + return false;
> +
> + return IS_GEN(dev_priv, 4) ||
Shouldn't this be INTEL_GEN() >= 4 || ... ? Or even this check alone as
first in the function.
> + IS_PINEVIEW(dev_priv) || IS_MOBILE(dev_priv);
> +}
> +
> static void i9xx_get_pfit_config(struct intel_crtc *crtc,
> struct intel_crtc_state *pipe_config)
> {
> struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> u32 tmp;
>
> - if (INTEL_GEN(dev_priv) <= 3 &&
> - (IS_I830(dev_priv) || !IS_MOBILE(dev_priv)))
> + if (!i9xx_has_pfit(dev_priv))
> return;
>
> tmp = I915_READ(PFIT_CONTROL);
>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-19 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 16:56 [PATCH 1/6] drm/i915: Reorder gen3/4 swizzle detection logic Ville Syrjala
2019-03-18 16:56 ` [PATCH 2/6] drm/i915: Introduce i9xx_has_pfit() Ville Syrjala
2019-03-19 13:24 ` Tvrtko Ursulin [this message]
2019-03-19 14:14 ` Ville Syrjälä
2019-03-19 14:23 ` [PATCH v2 " Ville Syrjala
2019-03-20 7:19 ` Tvrtko Ursulin
2019-03-18 16:56 ` [PATCH 3/6] drm/i915: Introduce i9xx_has_pps() Ville Syrjala
2019-03-19 13:26 ` Tvrtko Ursulin
2019-03-18 16:56 ` [PATCH 4/6] drm/i915: Introduce i915_has_asle() Ville Syrjala
2019-03-19 13:27 ` Tvrtko Ursulin
2019-03-18 16:56 ` [PATCH 5/6] drm/i915: Use HPLLVCO_MOBILE for all PNVs Ville Syrjala
2019-03-19 13:29 ` Tvrtko Ursulin
2019-03-20 15:27 ` Ville Syrjälä
2019-03-18 16:56 ` [PATCH 6/6] drm/i915: Clean up gen2 DPLL readout Ville Syrjala
2019-03-19 13:34 ` Tvrtko Ursulin
2019-03-19 14:17 ` Ville Syrjälä
2019-03-18 23:35 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Reorder gen3/4 swizzle detection logic Patchwork
2019-03-19 13:06 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-19 13:15 ` [PATCH 1/6] " Tvrtko Ursulin
2019-03-19 15:50 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Reorder gen3/4 swizzle detection logic (rev2) Patchwork
2019-03-20 0:40 ` ✓ Fi.CI.IGT: " Patchwork
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=d0c68085-e904-102e-2646-0061043a406c@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--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