From: mengdong.lin@linux.intel.com
To: alsa-devel@alsa-project.org, broonie@kernel.org
Cc: Mengdong Lin <mengdong.lin@linux.intel.com>,
tiwai@suse.de, mengdong.lin@intel.com,
guneshwor.o.singh@intel.com, liam.r.girdwood@intel.com,
hardik.t.shah@intel.com
Subject: [PATCH 6/6] topology: Update PCM configurations in Broadwell text conf file
Date: Thu, 28 Apr 2016 16:42:13 +0800 [thread overview]
Message-ID: <0864218d49edafe7b721cfe07b8bfa610bdb0a54.1461831763.git.mengdong.lin@linux.intel.com> (raw)
In-Reply-To: <cover.1461831763.git.mengdong.lin@linux.intel.com>
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To make this conf file a better example, update the name & ID of PCMs
(front-end DAI link) and their cpu DAI (front-end DAI), same as those
defined by Broadwell upstream driver.
Signed-off-by: Mengdong Lin <mengdong.lin@linux.intel.com>
diff --git a/src/conf/topology/broadwell/broadwell.conf b/src/conf/topology/broadwell/broadwell.conf
index 05b3889..eb89377 100644
--- a/src/conf/topology/broadwell/broadwell.conf
+++ b/src/conf/topology/broadwell/broadwell.conf
@@ -272,18 +272,22 @@ SectionPCMCapabilities."Offload0 Playback" {
SectionPCMCapabilities."Offload1 Playback" {
formats "S24_LE,S16_LE"
rate_min "8000"
- rate_max "48000"
+ rate_max "192000"
channels_min "2"
channels_max "2"
}
# PCM devices exported by Firmware
-SectionPCM."System Pin" {
+SectionPCM."System Playback/Capture" {
index "1"
# used for binding to the PCM
- ID "0"
+ id "0"
+
+ dai."System Pin" {
+ id "0"
+ }
pcm."playback" {
@@ -307,12 +311,16 @@ SectionPCM."System Pin" {
}
}
-SectionPCM."Offload0 Pin" {
+SectionPCM."Offload0 Playback" {
index "1"
# used for binding to the PCM
- ID "1"
+ id "1"
+
+ dai."Offload0 Pin" {
+ id "1"
+ }
pcm."playback" {
@@ -325,12 +333,16 @@ SectionPCM."Offload0 Pin" {
}
}
-SectionPCM."Offload1 Pin" {
+SectionPCM."Offload1 Playback" {
index "1"
# used for binding to the PCM
- ID "2"
+ id "2"
+
+ dai."Offload1 Pin" {
+ id "2"
+ }
pcm."playback" {
@@ -343,12 +355,16 @@ SectionPCM."Offload1 Pin" {
}
}
-SectionPCM."Loopback Pin" {
+SectionPCM."Loopback PCM" {
index "1"
# used for binding to the PCM
- ID "3"
+ id "3"
+
+ dai."Loopback Pin" {
+ id "3"
+ }
pcm."capture" {
--
2.5.0
prev parent reply other threads:[~2016-04-28 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 8:40 [PATCH 0/6] topology: complete PCM parsing and code refactoring mengdong.lin
2016-04-28 8:41 ` [PATCH 1/6] topology: Set manifest size for ABI mengdong.lin
2016-04-28 8:41 ` [PATCH 2/6] topology: Refactor functions to parse and build streams mengdong.lin
2016-04-28 8:41 ` [PATCH 3/6] topology: Use generic pointer to realloc buffer for private data mengdong.lin
2016-04-28 8:48 ` Jaroslav Kysela
2016-04-28 13:55 ` Takashi Iwai
2016-04-28 14:30 ` Lin, Mengdong
2016-05-04 1:29 ` Mengdong Lin
2016-05-08 9:52 ` Takashi Iwai
2016-04-28 8:41 ` [PATCH 4/6] topology: Fix pcm ID & name parsing mengdong.lin
2016-04-28 8:42 ` [PATCH 5/6] topology: Parse front-end DAI name and ID for the PCM mengdong.lin
2016-04-28 8:42 ` mengdong.lin [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=0864218d49edafe7b721cfe07b8bfa610bdb0a54.1461831763.git.mengdong.lin@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=hardik.t.shah@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=mengdong.lin@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).