From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, han.lu@intel.com
Cc: alsa-devel@alsa-project.org, mengdong.lin@linux.intel.com,
tiwai@suse.de, daniel.vetter@ffwll.ch,
intel-gfx@lists.freedesktop.org, han.lu@linux.intel.com,
libin.yang@linux.intel.com
Subject: Re: [PATCH V2 1/1] drm/i915/audio: apply SKL codec wake up patch to BXT
Date: Thu, 19 Nov 2015 18:01:51 +0200 [thread overview]
Message-ID: <87d1v6t1u8.fsf@intel.com> (raw)
In-Reply-To: <20151119155549.GJ17050@phenom.ffwll.local>
On Thu, 19 Nov 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Nov 19, 2015 at 10:44:48PM +0800, han.lu@intel.com wrote:
>> From: "Lu, Han" <han.lu@intel.com>
>>
>> For SKL we added a commit 632f3ab95fe2 ("drm/i915/audio: add codec wakeup
>> override enabled/disable callback"), in order to enable codec wakeup
>> override signal, to allow re-enumeration of the controller on SKL after
>> resume from low power state.
>> In SKL, HDMI/DP codec and PCH HD Audio Controller are in different power
>> wells, so it's necessary to reset display audio codecs when power well on,
>> otherwise display audio codecs will disappear when resume from low power
>> state.
>> Reset steps when power on:
>> enable codec wakeup -> azx_init_chip() -> disable codec wakeup
>> Since the power well design did not change from SKL to BXT, we need to
>> apply the workaround to BXT also.
>>
>> v2: add explanation
>>
>> Signed-off-by: Lu, Han <han.lu@intel.com>
>>
>> diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
>> index 63d4706..8310bf3 100644
>> --- a/drivers/gpu/drm/i915/intel_audio.c
>> +++ b/drivers/gpu/drm/i915/intel_audio.c
>> @@ -591,7 +591,8 @@ static void i915_audio_component_codec_wake_override(struct device *dev,
>> struct drm_i915_private *dev_priv = dev_to_i915(dev);
>> u32 tmp;
>>
>> - if (!IS_SKYLAKE(dev_priv) && !IS_KABYLAKE(dev_priv))
>> + if (!IS_SKYLAKE(dev_priv) && !IS_BROXTON(dev_priv) &&
>> + !IS_KABYLAKE(dev_priv))
>
> if (INTEL_INFO(dev)->gen < 9)
> return;
>
> for future-proofing? At least make it an IS_GEN9 check instead of
> listening all of them in a long list.
http://mid.gmane.org/87a8qacq5w.fsf@intel.com ...
> -Daniel
>
>> return;
>>
>> /*
>> --
>> 2.5.0
>>
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-11-19 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 14:44 [PATCH V2 1/1] drm/i915/audio: apply SKL codec wake up patch to BXT han.lu
2015-11-19 15:55 ` Daniel Vetter
2015-11-19 16:01 ` Jani Nikula [this message]
2015-11-20 1:16 ` Han Lu
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=87d1v6t1u8.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=han.lu@intel.com \
--cc=han.lu@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libin.yang@linux.intel.com \
--cc=mengdong.lin@linux.intel.com \
--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 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).