From: jeeja.kp@intel.com
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, patches.audio@intel.com, broonie@kernel.org,
liam.r.girdwood@intel.com, Jeeja KP <jeeja.kp@intel.com>
Subject: [RFC 16/16] ASoC: Intel: Skylake: To support MST, add HDMI routes da7219_max machine
Date: Tue, 20 Sep 2016 19:16:20 +0530 [thread overview]
Message-ID: <1474379180-7132-17-git-send-email-jeeja.kp@intel.com> (raw)
In-Reply-To: <1474379180-7132-1-git-send-email-jeeja.kp@intel.com>
From: Jeeja KP <jeeja.kp@intel.com>
Skylake platform support maximum of 3 ports per pin, so add the
additional routes for bxt_da7219_max98357a machine.
Signed-off-by: Jeeja KP <jeeja.kp@intel.com>
---
sound/soc/intel/boards/bxt_da7219_max98357a.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/sound/soc/intel/boards/bxt_da7219_max98357a.c b/sound/soc/intel/boards/bxt_da7219_max98357a.c
index c4dca26..5953c4f 100644
--- a/sound/soc/intel/boards/bxt_da7219_max98357a.c
+++ b/sound/soc/intel/boards/bxt_da7219_max98357a.c
@@ -84,7 +84,11 @@ static const struct snd_soc_dapm_route broxton_map[] = {
{"HDMI1", NULL, "hif5-0 Output"},
{"HDMI2", NULL, "hif6-0 Output"},
- {"HDMI2", NULL, "hif7-0 Output"},
+ {"HDMI2", NULL, "hif6-1 Output"},
+ {"HDMI2", NULL, "hif6-2 Output"},
+ {"HDMI3", NULL, "hif7-0 Output"},
+ {"HDMI3", NULL, "hif7-1 Output"},
+ {"HDMI3", NULL, "hif7-2 Output"},
{"hifi3", NULL, "iDisp3 Tx"},
{"iDisp3 Tx", NULL, "iDisp3_out"},
--
2.5.0
prev parent reply other threads:[~2016-09-20 13:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 13:46 [RFC 00/16] ASoC: hdac_hdmi: Add Support to Enable MST Audio jeeja.kp
2016-09-20 13:46 ` [RFC 01/16] ASoC: hdac_hdmi: use audio component framework to read ELD jeeja.kp
2016-09-25 5:58 ` Applied "ASoC: hdac_hdmi: use audio component framework to read ELD" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 02/16] ASoC: hdac_hdmi: Begin to add support for DP Multi-stream Audio jeeja.kp
2016-09-20 13:46 ` [RFC 03/16] ASoC: Intel: Skylake: Add route change to rt286 machine jeeja.kp
2017-02-04 12:12 ` Applied "ASoC: Intel: Skylake: Add route change to rt286 machine" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 04/16] ASoC: Intel: Skylake: Add route change to nau88l25_max98357a machine jeeja.kp
2017-02-08 18:34 ` Applied "ASoC: Intel: Skylake: Add route change to nau88l25_max98357a machine" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 05/16] ASoC: Intel: Skylake: Add route change to nau88l25_ssm4567 machine jeeja.kp
2017-02-08 18:34 ` Applied "ASoC: Intel: Skylake: Add route change to nau88l25_ssm4567 machine" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 06/16] ASoC: Intel: Skylake: Add route change to rt298 machine jeeja.kp
2017-02-08 18:34 ` Applied "ASoC: Intel: bxt: Add route change to rt298 machine" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 07/16] ASoC: Intel: Skylake: Add route change to da7219_max98357a machine jeeja.kp
2017-02-04 12:12 ` Applied "ASoC: Intel: bxt: Add route change to da7219_max98357a machine" to the asoc tree Mark Brown
2016-09-20 13:46 ` [RFC 08/16] ASoC: hdac_hdmi: Add support to handle MST capable pin jeeja.kp
2016-09-20 13:46 ` [RFC 09/16] ASoC: hdac_hdmi: Add MST verb support jeeja.kp
2016-09-20 13:46 ` [RFC 10/16] ASoc: hdac_hdmi: Configure pin verbs for MST jeeja.kp
2016-09-20 13:46 ` [RFC 11/16] ASoC: hdac_hdmi: Add support to handle Multiple Port to same PCM jeeja.kp
2016-09-20 13:46 ` [RFC 12/16] ASoC: Intel: Skylake: To support MST, add HDMI routes rt286 machine jeeja.kp
2016-09-20 13:46 ` [RFC 13/16] ASoC: Intel: Skylake: To support MST, add HDMI routes nau_max machine jeeja.kp
2016-09-20 13:46 ` [RFC 14/16] ASoC: Intel: Skylake: To support MST, add HDMI routes nau_ssm machine jeeja.kp
2016-09-20 13:46 ` [RFC 15/16] ASoC: Intel: Skylake: To support MST, add HDMI routes rt298 machine jeeja.kp
2016-09-20 13:46 ` jeeja.kp [this message]
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=1474379180-7132-17-git-send-email-jeeja.kp@intel.com \
--to=jeeja.kp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=patches.audio@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).