From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Bob Paauwe <bob.j.paauwe@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Get audio power domain during initial hw readout
Date: Wed, 13 Apr 2016 11:59:43 +0300 [thread overview]
Message-ID: <20160413085943.GZ4329@intel.com> (raw)
In-Reply-To: <1460501568-29102-1-git-send-email-bob.j.paauwe@intel.com>
On Tue, Apr 12, 2016 at 03:52:48PM -0700, Bob Paauwe wrote:
> if the crtc has audio is enabled. Otherwise, when the first atomic
> modeset happens it will warn when trying to drop the audio power
> domain.
>
> Signed-off-by: Bob Paauwe <bob.j.paauwe@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 5155efb6..caeb3e1 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -10561,6 +10561,7 @@ found:
> }
>
> ret = intel_modeset_setup_plane_state(state, crtc, mode, fb, 0, 0);
> +
> if (ret)
> goto fail;
>
> @@ -15998,6 +15999,10 @@ static void intel_modeset_readout_hw_state(struct drm_device *dev)
>
> memset(&crtc->base.mode, 0, sizeof(crtc->base.mode));
> if (crtc->base.state->active) {
> + if (crtc->config->has_audio)
> + intel_display_power_get(dev_priv,
> + POWER_DOMAIN_AUDIO);
> +
Hmm. Ideally we would do this alongside the other power doamin stuff in
intel_modeset_setup_hw_state(), but that's too late for
intel_sanitize_{crtc,encoder}(). So I guess we'll have to do it before
those, or we have to pull the audio power domain stuff out from the
encoder hooks. Or perhaps even throw it out entirely, since I'm not sure
it's doing anything for us.
If we do leave the power domain handling in the encoder hooks, then
this is not quite the right place to grab the reference. We could have
an encoder enabled w/o an active pipe, in which case
intel_sanitize_encoder() would shut off the encoder, so we'd still end
up with a bad refcount.
> intel_mode_from_pipe_config(&crtc->base.mode, crtc->config);
> intel_mode_from_pipe_config(&crtc->base.state->adjusted_mode, crtc->config);
> WARN_ON(drm_atomic_set_mode_for_crtc(crtc->base.state, &crtc->base.mode));
> --
> 2.5.5
>
> _______________________________________________
> 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:[~2016-04-13 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 22:52 [PATCH] drm/i915: Get audio power domain during initial hw readout Bob Paauwe
2016-04-13 8:59 ` Ville Syrjälä [this message]
2016-04-13 18:19 ` Bob Paauwe
2016-04-13 18:27 ` Ville Syrjälä
2016-04-20 20:43 ` Bob Paauwe
2016-04-13 16:29 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-20 20:38 ` [PATCH] drm/i915: Get audio power domain during initial hw readout (v2) Bob Paauwe
2016-04-22 16:40 ` [isg-gms] " Xiong, James
2016-04-21 14:02 ` ✗ Fi.CI.BAT: failure for drm/i915: Get audio power domain during initial hw readout (rev2) Patchwork
2016-04-23 12:23 ` ✓ Fi.CI.BAT: success " 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=20160413085943.GZ4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=bob.j.paauwe@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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