OrgACRN
/
sof
mirror of https://github.com/thesofproject/sof.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
sof/tools/topology/sof-apl-demux-pcm512x.m4

160 lines
4.0 KiB
Plaintext
Raw Normal View History

topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
#
# Demux topology for generic Apollolake UP^2 with pcm512x codec and HDMI.
#
# Include topology builder
include(`utils.m4')
include(`dai.m4')
include(`pipeline.m4')
include(`ssp.m4')
# Include TLV library
include(`common/tlv.m4')
# Include Token library
include(`sof/tokens.m4')
# Include Apollolake DSP configuration
include(`platform/intel/bxt.m4')
DEBUG_START
#
# Define the pipelines
#
# PCM0 ----> demux -----> SSP5 (pcm512x)
# PCM1 ----> volume -----> iDisp1
# PCM2 ----> volume -----> iDisp2
# PCM3 ----> volume -----> iDisp3
# PCM4 <---- demux
#
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
dnl PIPELINE_PCM_ADD(pipeline,
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
dnl pipe id, pcm, max channels, format,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
dnl period, priority, core,
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
dnl pcm_min_rate, pcm_max_rate, pipeline_rate,
dnl time_domain, sched_comp)
topology: apl: glk: use 3 periods for SSP and DMIC DAIs Changes number of SSP and DMIC DAI periods from 2 to 3. This way we can support both timer and new single DMA channel scheduling. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-09-19 22:19:49 +08:00
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Demux pipeline 1 on PCM 0 using max 2 channels of s32le.
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Set 1000us deadline on core 0 with priority 0
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
PIPELINE_PCM_ADD(sof/pipe-volume-demux-playback.m4,
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
1, 0, 2, s32le,
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
1000, 0, 0,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
48000, 48000, 48000)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Low Latency playback pipeline 2 on PCM 1 using max 2 channels of s32le.
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Set 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
PIPELINE_PCM_ADD(sof/pipe-volume-playback.m4,
2, 1, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0,
48000, 48000, 48000)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Low Latency playback pipeline 3 on PCM 2 using max 2 channels of s32le.
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Set 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
PIPELINE_PCM_ADD(sof/pipe-volume-playback.m4,
3, 2, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0,
48000, 48000, 48000)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Low Latency playback pipeline 4 on PCM 3 using max 2 channels of s32le.
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Set 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
PIPELINE_PCM_ADD(sof/pipe-volume-playback.m4,
4, 3, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0,
48000, 48000, 48000)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
#
# DAIs configuration
#
dnl DAI_ADD(pipeline,
dnl pipe id, dai type, dai_index, dai_be,
dnl buffer, periods, format,
topology: apl: glk: use 3 periods for SSP and DMIC DAIs Changes number of SSP and DMIC DAI periods from 2 to 3. This way we can support both timer and new single DMA channel scheduling. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-09-19 22:19:49 +08:00
dnl deadline, priority, core, time_domain)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
# playback DAI is SSP5 using 2 periods
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Buffers use s24le format, 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
DAI_ADD(sof/pipe-dai-playback.m4,
1, SSP, 5, SSP5-Codec,
topology: revert all cAVS pipelines to 2 periods Reverts all previosly changed cAVS pipelines from 3 to 2 periods. Now we have separate buffers for DMA, so there is no need to make DAI buffers consist of 3 periods. DMA will take care of any internal hardware requirements. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-22 15:09:58 +08:00
PIPELINE_SOURCE_1, 2, s24le,
topology: cavs: switch all pipelines to timer scheduling Switches all pipelines for cAVS platforms to timer scheduling. This way we limit the number of interrupt levels processed in the system. Timer, IPC and IDC are already on level 2 and DMAs are on level 5. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-15 19:40:26 +08:00
1000, 0, 0, SCHEDULE_TIME_DOMAIN_TIMER)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# currently this dai is here as "virtual" capture backend
topology: apl: glk: use 3 periods for SSP and DMIC DAIs Changes number of SSP and DMIC DAI periods from 2 to 3. This way we can support both timer and new single DMA channel scheduling. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-09-19 22:19:49 +08:00
W_DAI_IN(SSP, 5, SSP5-Codec, s24le, 3, 0)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Capture pipeline 5 from demux on PCM 5 using max 2 channels of s32le.
PIPELINE_PCM_ADD(sof/pipe-passthrough-capture-sched.m4,
5, 4, 2, s32le,
topology: fix connected pipelines' priorities Fixes pipelines' priorities in multipipe topologies. The highest priority is 0. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-10 18:47:56 +08:00
1000, 1, 0,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
48000, 48000, 48000,
topology: cavs: switch all pipelines to timer scheduling Switches all pipelines for cAVS platforms to timer scheduling. This way we limit the number of interrupt levels processed in the system. Timer, IPC and IDC are already on level 2 and DMAs are on level 5. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
2019-10-15 19:40:26 +08:00
SCHEDULE_TIME_DOMAIN_TIMER,
PIPELINE_PLAYBACK_SCHED_COMP_1)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# Connect demux to capture
SectionGraph."PIPE_CAP" {
index "0"
lines [
# mux to capture
dapm(PIPELINE_SINK_5, PIPELINE_DEMUX_1)
]
}
# Connect virtual capture to dai
SectionGraph."PIPE_CAP_VIRT" {
index "5"
lines [
# mux to capture
dapm(ECHO REF 5, SSP5.IN)
]
}
# playback DAI is iDisp1 using 2 periods
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Buffers use s32le format, 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
DAI_ADD(sof/pipe-dai-playback.m4,
2, HDA, 0, iDisp1,
PIPELINE_SOURCE_2, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0, SCHEDULE_TIME_DOMAIN_TIMER)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# playback DAI is iDisp2 using 2 periods
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Buffers use s32le format, 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
DAI_ADD(sof/pipe-dai-playback.m4,
3, HDA, 1, iDisp2,
PIPELINE_SOURCE_3, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0, SCHEDULE_TIME_DOMAIN_TIMER)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# playback DAI is iDisp3 using 2 periods
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
# Buffers use s32le format, 1000us deadline on core 0 with priority 0
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
DAI_ADD(sof/pipe-dai-playback.m4,
4, HDA, 2, iDisp3,
PIPELINE_SOURCE_4, 2, s32le,
topology: enable pcm range and pipeline rate and remove frame count Enable setting pcm min and max rate from top level m4 pipeline macro. This way it is possible to configure the whole pipeline to correct samplerate range in 1 file. Previously you needed to modify the pipeline macros where the rate was hardcoded. As the frame count is calculated from pcm/dai rate and scheduling time the frame count is obsolete. Introduce pipeline rate parameter to help configuring components with fixed output rate. We can't deduce this from pcm range since for example src might accept bigger max rate than the following dai. Even though the parameter is named "pipeline rate" it essentially means the "final" output rate to which this pipeline is connected to (dai or other pipeline). In capture pipelines it means the originating fixed dai rate. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-01-03 20:11:21 +08:00
1000, 0, 0, SCHEDULE_TIME_DOMAIN_TIMER)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
# PCM Low Latency, id 0
dnl PCM_PLAYBACK_ADD(name, pcm_id, playback)
PCM_PLAYBACK_ADD(Port5, 0, PIPELINE_PCM_1)
PCM_PLAYBACK_ADD(HDMI1, 1, PIPELINE_PCM_2)
PCM_PLAYBACK_ADD(HDMI2, 2, PIPELINE_PCM_3)
PCM_PLAYBACK_ADD(HDMI3, 3, PIPELINE_PCM_4)
PCM_CAPTURE_ADD(EchoRef, 4, PIPELINE_PCM_5)
#
# BE configurations - overrides config in ACPI if present
#
#SSP 5 (ID: 0)
DAI_CONFIG(SSP, 5, 0, SSP5-Codec,
SSP_CONFIG(I2S, SSP_CLOCK(mclk, 24576000, codec_mclk_in),
SSP_CLOCK(bclk, 3072000, codec_slave),
SSP_CLOCK(fsync, 48000, codec_slave),
SSP_TDM(2, 32, 3, 3),
SSP_CONFIG_DATA(SSP, 5, 24)))
topology: fix apl-demux-pcm512x HDMI dai id The HDMI DAI id changed, update the demux topology. Signed-off-by: Pan Xiuli <xiuli.pan@linux.intel.com>
2020-03-11 15:59:28 +08:00
# 3 HDMI/DP outputs (ID: 3,4,5)
DAI_CONFIG(HDA, 0, 3, iDisp1)
DAI_CONFIG(HDA, 1, 4, iDisp2)
DAI_CONFIG(HDA, 2, 5, iDisp3)
topology: add demux topology for apl and cml This topology will add a capture branch back from playback pipeline's mux component. It can be used for example as a echo cancellation reference signal. Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
2019-04-24 02:24:06 +08:00
DEBUG_END