All of lore.kernel.org
 help / color / mirror / Atom feed
From: han.lu@intel.com
To: tiwai@suse.de, libin.yang@linux.intel.com,
	mengdong.lin@linux.intel.com, han.lu@linux.intel.com,
	alsa-devel@alsa-project.org
Cc: "Lu, Han" <han.lu@intel.com>
Subject: [PATCH 2/2] ALSA: hda - apply SKL display power request/release patch to BXT
Date: Thu, 19 Nov 2015 23:25:13 +0800	[thread overview]
Message-ID: <7a931eac5852ad6c303caeb4d0c9274e1133a09b.1447945222.git.han.lu@intel.com> (raw)
In-Reply-To: <cover.1447945222.git.han.lu@intel.com>
In-Reply-To: <cover.1447945222.git.han.lu@intel.com>

From: "Lu, Han" <han.lu@intel.com>

For SKL, only the HDMI codec is in the display power well while the
HD-A controller isn't. So the codec flag 'link_power_control' is
set to request/release the display power via bus link_power ops.
For BXT, the power well design is the same as SKL, so the patch
should be applied to BXT too.

Signed-off-by: Lu, Han <han.lu@intel.com>

diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index 309274b..aa68db6 100644
--- a/sound/pci/hda/patch_hdmi.c
+++ b/sound/pci/hda/patch_hdmi.c
@@ -2375,7 +2375,8 @@ static int patch_generic_hdmi(struct hda_codec *codec)
 	 * can cover the codec power request, and so need not set this flag.
 	 * For previous platforms, there is no such power well feature.
 	 */
-	if (is_valleyview_plus(codec) || is_skylake(codec))
+	if (is_valleyview_plus(codec) || is_skylake(codec) ||
+			is_broxton(codec))
 		codec->core.link_power_control = 1;
 
 	if (is_haswell_plus(codec) || is_valleyview_plus(codec)) {
-- 
2.5.0

  parent reply	other threads:[~2015-11-19 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 15:25 [PATCH 0/2] Add ID and patches for Intel BXT han.lu
2015-11-19 15:25 ` [PATCH 1/2] ALSA: hda - add PCI IDs for Intel Broxton han.lu
2015-11-19 15:25 ` han.lu [this message]
2015-11-19 15:43 ` [PATCH 0/2] Add ID and patches for Intel BXT Takashi Iwai

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=7a931eac5852ad6c303caeb4d0c9274e1133a09b.1447945222.git.han.lu@intel.com \
    --to=han.lu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=han.lu@linux.intel.com \
    --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 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.