From: Matt Roper <matthew.d.roper@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 04/24] drm/i915: Update power domains only on affected crtc's.
Date: Tue, 2 Jun 2015 18:27:52 -0700 [thread overview]
Message-ID: <20150603012752.GD17555@intel.com> (raw)
In-Reply-To: <1433165247-15928-5-git-send-email-maarten.lankhorst@linux.intel.com>
On Mon, Jun 01, 2015 at 03:27:07PM +0200, Maarten Lankhorst wrote:
> Use for_each_crtc_state to only touch affected crtc's.
> In order to make sure that the initial power is still set
> correctly we make sure modeset_update_crtc_power_domains is called
> during the initial modeset.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 3 ---
> drivers/gpu/drm/i915/intel_display.c | 41 +++++++++++++++++++++++-------------
> 2 files changed, 26 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index d3632c56fdf7..78ef0bb53c36 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -634,9 +634,6 @@ static int i915_drm_suspend(struct drm_device *dev)
> intel_display_suspend(dev);
> drm_modeset_unlock_all(dev);
>
> - /* suspending displays will unsets init power */
> - intel_display_set_init_power(dev_priv, true);
> -
> intel_dp_mst_suspend(dev);
>
> intel_runtime_pm_disable_interrupts(dev_priv);
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 8e9afc55c284..4dc07602248b 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5188,42 +5188,49 @@ static unsigned long get_crtc_power_domains(struct drm_crtc *crtc)
> return mask;
> }
>
> -static void modeset_update_crtc_power_domains(struct drm_atomic_state *state)
> +static void modeset_update_crtc_power_domains(struct drm_atomic_state *state, bool gr)
What does 'gr' stand for and what does the parameter signify? It seems
to just gate whether we call display.modeset_global_resources, but it's
unclear to me from the commit message above in which situations we
would/wouldn't want to do this and why.
Matt
> {
> struct drm_device *dev = state->dev;
> struct drm_i915_private *dev_priv = dev->dev_private;
> - unsigned long pipe_domains[I915_MAX_PIPES] = { 0, };
> - struct intel_crtc *crtc;
> + unsigned long pipe_domains[I915_MAX_PIPES] = { 0, }, domains;
> + struct drm_crtc_state *crtc_state;
> + struct drm_crtc *crtc;
> + int i;
>
> /*
> * First get all needed power domains, then put all unneeded, to avoid
> * any unnecessary toggling of the power wells.
> */
> - for_each_intel_crtc(dev, crtc) {
> + for_each_crtc_in_state(state, crtc, crtc_state, i) {
> enum intel_display_power_domain domain;
> + enum pipe pipe = to_intel_crtc(crtc)->pipe;
>
> - if (!crtc->base.state->enable)
> + if (!crtc->state->active)
> continue;
>
> - pipe_domains[crtc->pipe] = get_crtc_power_domains(&crtc->base);
> + domains = pipe_domains[pipe] = get_crtc_power_domains(crtc);
> + domains &= ~to_intel_crtc(crtc)->enabled_power_domains;
>
> - for_each_power_domain(domain, pipe_domains[crtc->pipe])
> + for_each_power_domain(domain, domains)
> intel_display_power_get(dev_priv, domain);
> }
>
> - if (dev_priv->display.modeset_global_resources)
> + if (gr && dev_priv->display.modeset_global_resources)
> dev_priv->display.modeset_global_resources(state);
>
> - for_each_intel_crtc(dev, crtc) {
> + for_each_crtc_in_state(state, crtc, crtc_state, i) {
> + struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
> + enum pipe pipe = intel_crtc->pipe;
> enum intel_display_power_domain domain;
>
> - for_each_power_domain(domain, crtc->enabled_power_domains)
> - intel_display_power_put(dev_priv, domain);
> + domains = intel_crtc->enabled_power_domains;
> + domains &= ~pipe_domains[pipe];
>
> - crtc->enabled_power_domains = pipe_domains[crtc->pipe];
> - }
> + intel_crtc->enabled_power_domains = pipe_domains[pipe];
>
> - intel_display_set_init_power(dev_priv, false);
> + for_each_power_domain(domain, domains)
> + intel_display_power_put(dev_priv, domain);
> + }
> }
>
> void broxton_set_cdclk(struct drm_device *dev, int frequency)
> @@ -12698,7 +12705,7 @@ static int __intel_set_mode(struct drm_atomic_state *state)
> /* The state has been swaped above, so state actually contains the
> * old state now. */
>
> - modeset_update_crtc_power_domains(state);
> + modeset_update_crtc_power_domains(state, true);
>
> /* Now enable the clocks, plane, pipe, and connectors that we set up. */
> for_each_crtc_in_state(state, crtc, crtc_state, i) {
> @@ -15280,12 +15287,16 @@ void intel_modeset_setup_hw_state(struct drm_device *dev,
> ret = intel_set_mode(state);
> if (ret) {
> DRM_ERROR("Failed to restore previous mode\n");
> + modeset_update_crtc_power_domains(state, false);
> drm_atomic_state_free(state);
> }
> } else {
> + modeset_update_crtc_power_domains(state, false);
> drm_atomic_state_free(state);
> }
>
> + intel_display_set_init_power(dev_priv, false);
> +
> intel_modeset_check_state(dev);
> }
>
> --
> 2.1.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-03 1:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:27 [PATCH 00/24] Convert to atomic, part 3 Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 01/24] drm/i915: Always reset in intel_crtc_restore_mode Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 02/24] drm/i915: Use crtc state in intel_modeset_pipe_config Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 03/24] drm/i915: clean up intel_sanitize_crtc Maarten Lankhorst
2015-06-03 1:27 ` Matt Roper
2015-06-03 6:47 ` Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 04/24] drm/i915: Update power domains only on affected crtc's Maarten Lankhorst
2015-06-03 1:27 ` Matt Roper [this message]
2015-06-03 6:52 ` Maarten Lankhorst
2015-06-15 11:43 ` Daniel Vetter
2015-06-15 11:49 ` Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 05/24] drm/i915: add fastboot checks for has_audio and has_infoframe Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 06/24] drm/i915: Clean up intel_atomic_setup_scalers slightly Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 07/24] drm/i915: Add a simple atomic crtc check function Maarten Lankhorst
2015-06-03 1:28 ` Matt Roper
2015-06-03 6:56 ` Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 08/24] drm/i915: Do not add planes from intel_atomic_setup_scalers Maarten Lankhorst
2015-06-03 1:29 ` Matt Roper
2015-06-03 1:52 ` Konduru, Chandra
2015-06-03 7:01 ` Maarten Lankhorst
2015-06-03 19:32 ` Konduru, Chandra
2015-06-03 23:33 ` Matt Roper
2015-06-04 3:39 ` Maarten Lankhorst
2015-06-05 19:05 ` Konduru, Chandra
2015-06-06 6:39 ` Maarten Lankhorst
2015-06-08 17:25 ` Konduru, Chandra
2015-06-15 11:48 ` Daniel Vetter
2015-06-01 13:27 ` [PATCH 09/24] drm/i915: Assign a new pll from the crtc check function Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 10/24] drm/i915: Do not run most checks when there's no modeset Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 11/24] drm/i915: Split skl_update_scaler Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 12/24] drm/i915: Split plane updates of crtc->atomic into a helper Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 13/24] drm/i915: move detaching scalers to begin_crtc_commit Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 14/24] drm/i915: Move crtc commit updates to separate functions Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 15/24] drm/i915: clean up plane commit functions Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 16/24] drm/i915: atomic plane updates in a nutshell Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 17/24] drm/i915: Update less state during modeset Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 18/24] drm/i915: get rid of intel_plane_restore in intel_crtc_page_flip Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 19/24] drm/i915: Make setting color key atomic Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 20/24] drm/i915: clean up atomic plane check functions Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 21/24] drm/i915: remove force argument from disable_plane Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 22/24] drm/i915: Use full atomic modeset Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 23/24] drm/i915: Unify plane updates Maarten Lankhorst
2015-06-01 13:27 ` [PATCH 24/24] drm/i915: always disable irqs in intel_pipe_update_start Maarten Lankhorst
2015-06-02 9:34 ` [PATCH 00/24] Convert to atomic, part 3 Maarten Lankhorst
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=20150603012752.GD17555@intel.com \
--to=matthew.d.roper@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