From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/3] drm/i915: Enable IPS with only sprite plane visible too, v2.
Date: Mon, 20 Nov 2017 15:27:59 +0200 [thread overview]
Message-ID: <20171120132759.GU10981@intel.com> (raw)
In-Reply-To: <20171120122337.1587-3-maarten.lankhorst@linux.intel.com>
On Mon, Nov 20, 2017 at 01:23:36PM +0100, Maarten Lankhorst wrote:
> This comment predates atomic, and I think with the way we currently
> track IPS, it's safe to enable this for the case we switch too.
>
> Changes since v1:
> - Keep IPS enabled when switching planes.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 0b9ba415839a..09817bc6f9a8 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -6237,13 +6237,8 @@ static bool hsw_compute_ips_config(struct intel_crtc_state *pipe_config)
> if (pipe_config->ips_force_disable)
> return false;
>
> - /*
> - * FIXME IPS should be fine as long as one plane is
> - * enabled, but in practice it seems to have problems
> - * when going from primary only to sprite only and vice
> - * versa.
> - */
> - if (!(pipe_config->active_planes & BIT(PLANE_PRIMARY)))
> + /* IPS should be fine as long as one plane is enabled. */
Maybe "... at least one plane is enabled." to make it less vague?
> + if (hweight32(pipe_config->active_planes & ~BIT(PLANE_CURSOR)) != 1)
I keep wondering if popcnt is cheaper than is_power_of_2()? If it is,
maybe someone should actually make is_power_of_2() use popcnt...
> return false;
>
> /* HSW can handle pixel rate up to cdclk? */
> --
> 2.15.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-20 13:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 12:23 [PATCH v2 0/3] drm/i915: Enable fastboot, v3! Maarten Lankhorst
2017-11-20 12:23 ` [PATCH v2 1/3] drm/i915: Make ips_enabled a property depending on whether IPS is enabled, v2 Maarten Lankhorst
2017-11-20 14:01 ` Ville Syrjälä
2017-11-20 16:21 ` Maarten Lankhorst
2017-11-22 15:07 ` [PATCH] drm/i915: Make ips_enabled a property depending on whether IPS is enabled, v3 Maarten Lankhorst
2017-11-22 15:34 ` Ville Syrjälä
2017-11-22 18:39 ` [PATCH 1/2] " Maarten Lankhorst
2017-11-23 14:36 ` Ville Syrjälä
2017-11-30 15:54 ` Maarten Lankhorst
2017-11-20 12:23 ` [PATCH v2 2/3] drm/i915: Enable IPS with only sprite plane visible too, v2 Maarten Lankhorst
2017-11-20 13:27 ` Ville Syrjälä [this message]
2017-11-21 9:27 ` Maarten Lankhorst
2017-11-22 15:08 ` [PATCH] drm/i915: Enable IPS with only sprite plane visible too, v3 Maarten Lankhorst
2017-11-22 15:28 ` Ville Syrjälä
2017-11-22 18:39 ` [PATCH 2/2] drm/i915: Enable IPS with only sprite plane visible too, v4 Maarten Lankhorst
2017-11-23 14:37 ` Ville Syrjälä
2017-11-20 12:23 ` [PATCH (resend) 3/3] drm/i915: Re-enable fastboot by default Maarten Lankhorst
2017-11-20 13:05 ` ✓ Fi.CI.BAT: success for drm/i915: Enable fastboot, v3! Patchwork
2017-11-20 14:15 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-22 15:38 ` ✗ Fi.CI.BAT: failure for drm/i915: Enable fastboot, v3! (rev3) Patchwork
2017-11-22 19:27 ` ✓ Fi.CI.BAT: success for drm/i915: Enable fastboot, v3! (rev5) Patchwork
2017-11-22 21:11 ` ✓ 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=20171120132759.GU10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@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;
as well as URLs for NNTP newsgroup(s).