topology: Define new type and section name to configure physical links

Users may not use DPCM but still need to configure the physical links.
So we should not only consider backend links for DPCM.

- SND_TPLG_TYPE_LINK is defined to configure physical links by C API.
  And SND_TPLG_TYPE_BE is still supported to configure Backend links for
  DPCM cases.

- SectionLink can be used to configure physical links in text conf file.
  And SectionBE is still supported to config Backend links for DPCM cases.

Actually, users can use SND_TPLG_TYPE_LINK and SectionLink to configure
backend links for DPCM cases, because BE links are also physical links.
The parsing is same and we rename the function from tplg_parse_be to
tplg_parse_link.

Signed-off-by: Mengdong Lin <mengdong.lin@linux.intel.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
This commit is contained in:
Mengdong Lin 2016-11-06 13:13:36 +08:00 committed by Takashi Iwai
parent cb9451b8e7
commit f5b275b24c
4 changed files with 29 additions and 10 deletions

View file

@ -617,6 +617,24 @@ extern "C" {
* }
* </pre>
*
* <h4>Physical DAI Link Configurations</h4>
* The runtime configurations of a physical DAI link can be defined by
* SectionLink. <br> Backend DAI links belong to physical links, and can
* be configured by either SectionLink or SectionBE, with same syntax.
* But SectionBE is deprecated atm since the internal processing is
* actually same.
*
* <pre>
* SectionLink."name" {
*
* index "1" # Index number
*
* id "0" # used for binding to the link
*
* data "name" # optional private data
* }
* </pre>
*
* <h4>Manifest Private Data</h4>
* Manfiest may have private data. Users need to define a manifest section
* and add the references to 1 or multiple data sections. Please refer to
@ -687,6 +705,7 @@ enum snd_tplg_type {
SND_TPLG_TYPE_MANIFEST, /*!< Topology manifest */
SND_TPLG_TYPE_TOKEN, /*!< Vendor tokens */
SND_TPLG_TYPE_TUPLE, /*!< Vendor tuples */
SND_TPLG_TYPE_LINK, /*!< Physical DAI link */
};
/**