From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] drm/i915: Acquire intel_runtime_pm for HD-Audio registers
Date: Tue, 12 Jul 2016 16:10:22 +0300 [thread overview]
Message-ID: <87zipnroht.fsf@intel.com> (raw)
In-Reply-To: <1468058747-31160-1-git-send-email-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Haswell/Broadwell, the HD-Audio block is inside the HDMI/display
> power well and so the sna-hda audio codec acquires the display power
> well while it is operational. However, Skylake separates the powerwells
> again, and so we must remember to acquire the rpm wakeref for ourselves
> whilst tweaking the registers.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96214
> Fixes: 03b135cebc47 "ALSA: hda - remove dependency on i915 power well for SKL")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
> Cc: Libin Yang <libin.yang@intel.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: Marius Vlad <marius.c.vlad@intel.com>
> ---
> drivers/gpu/drm/i915/intel_audio.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
> index 5d5f6bc10e85..eedcce6478ef 100644
> --- a/drivers/gpu/drm/i915/intel_audio.c
> +++ b/drivers/gpu/drm/i915/intel_audio.c
> @@ -600,6 +600,8 @@ static void i915_audio_component_codec_wake_override(struct device *dev,
> if (!IS_SKYLAKE(dev_priv) && !IS_KABYLAKE(dev_priv))
> return;
>
> + intel_runtime_pm_get(dev_priv);
> +
> /*
> * Enable/disable generating the codec wake signal, overriding the
> * internal logic to generate the codec wake to controller.
> @@ -615,6 +617,8 @@ static void i915_audio_component_codec_wake_override(struct device *dev,
> I915_WRITE(HSW_AUD_CHICKENBIT, tmp);
> usleep_range(1000, 1500);
> }
> +
> + intel_runtime_pm_put(dev_priv);
> }
>
> /* Get CDCLK in kHz */
> @@ -648,6 +652,8 @@ static int i915_audio_component_sync_audio_rate(struct device *dev,
> !IS_HASWELL(dev_priv))
> return 0;
>
> + intel_runtime_pm_get(dev_priv);
> +
> mutex_lock(&dev_priv->av_mutex);
> /* 1. get the pipe */
> intel_encoder = dev_priv->dig_port_map[port];
> @@ -698,6 +704,7 @@ static int i915_audio_component_sync_audio_rate(struct device *dev,
>
> unlock:
> mutex_unlock(&dev_priv->av_mutex);
> + intel_runtime_pm_put(dev_priv);
> return err;
> }
>
> --
> 2.8.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-12 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 10:05 [PATCH] drm/i915: Acquire intel_runtime_pm for HD-Audio registers Chris Wilson
2016-07-09 10:48 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-12 13:10 ` Mika Kuoppala [this message]
2016-07-12 13:16 ` [PATCH] " Chris Wilson
2016-07-13 14:01 ` Marius Vlad
2016-07-14 14:34 ` Chris Wilson
2016-07-15 2:40 ` Yang, Libin
2016-07-15 8:44 ` Chris Wilson
2016-07-16 7:06 ` Yang, Libin
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=87zipnroht.fsf@intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.