Zephyr also a version.h too so the situation was a buggy #include mess
that (among others) dropped the SOF git version from the SOF banner when
using Zephyr. It's absolutely impossible to fix this mess while keeping
two .h files both named exactly the same and even included with the
exact same '#include version.h' line, I mean no sof/version.h or other
prefix.
As a bonus, this rename also reduces the XTOS-only confusion between
"version.h" and cavs/version.h".
Generating a file in the source tree is a serious bug (to be fixed
later), it means this file is never cleaned. Do not hide this bug with a
.gitignore rule.
Signed-off-by: Marc Herbert <marc.herbert@intel.com>
So far we support apl, glk, cml, jsl, tgl.
SSP0 or SSP2 can be used.
DMICS may or may not be present, the simplifying assumption is that we
have 0, 2 or 4channels.
the existing topology names are kept but will not be used with kernel
updates, the -ssp<N> and -dmic<N> ch suffixes will be added based on
NHLT information to avoid a need to override topology files.
A better solution would be a DAI index that can be overridden in a
topology file, but we have no interface to do so at the moment, so
brute-force combinatorial handling of all possible solutions it is.
Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
set the state to MODULE_PROCESSING before starting to process the
samples and reset it to MODULE_IDLE afterwards.
Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
SOF loves memset(). It takes great care to 0-initialise buffers and
objects. And its memset() routine only sets one byte at a time.
Optimise it to use 32-bit assignments where possible.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
base_module and boot_module are separate targets, they need
RELATIVE_FILE defined for them too.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
Components those use library functions fail to run in testbench
if they are not enabled in library_defconfig. The testbench build
builds the component library but not the library dependencies. E.g.
DRC component run in testbench failed because of this. Crossover
worked because it does not currently use library functions. All such
components with functional source are enabled for completeness.
Signed-off-by: Seppo Ingalsuo <seppo.ingalsuo@linux.intel.com>
Currently pipeline reset is used by ipc3 for pipeline
free and pcm param error. It is used by ipc4 to
reinitialize pipeline, so it suitable to set pipeline
to default ready status
Signed-off-by: Rander Wang <rander.wang@intel.com>
Chain dma is only support by HDA gateway. The idea is
to copy data from host to dai directly without any process.
It is just like a pass-through pipeline.
This patch adds support by create a pass-through pipeline
internally.
Signed-off-by: Rander Wang <rander.wang@intel.com>
Currently some of pipeline setting ipc messages are
scheduled in another thread, both ipc thread and the
schedule thread may return the status. It is work for
IPC3, but for IPC4 a batch of pipelines will be set
by single ipc message and they will be scheduled in
multiple threads, then multiple ipc messages will be
repied to host. This is invalid.
In this case error may occur in both ipc thread and
schedule thread. To update err status simple, schedule
thread will only return error to ipc thread which will
maintain error status and reply to host.
Signed-off-by: Rander Wang <rander.wang@intel.com>
(1) IPC4 does not need mixer workaround.
(2) trigger pipeline in release state for pause-running case
Signed-off-by: Rander Wang <rander.wang@intel.com>
Modify module_load_config() to handle both setup and runtime configs and
remove load_setup_config().
Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Check if more fragments of config data are expected first and return
immediately to make the code easier to follow.
Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Remove the goto's and return the appropriate values to simplify the
codec_adapter_set_params() function.
Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Let's enable this capability, with CAVS_1_5 left out for now since there
are known issues with suspend-resume on Up2 board that were never
root-caused.
Enabling this at the firmware level is not enough, this capability
need to be enabled by kernel patches in
https://github.com/thesofproject/linux/pull/3340
Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
In order to ease comprehension and avoid side-effect of constants being
defined after calling a macro, this change undefined the locally define
constants for pipelines and dai macros.
Signed-off-by: Lionel Koenig <lionelk@google.com>
All SSP drivers handle COMP_TRIGGER_RELEASE and COMP_TRIGGER_START in
the same way. Similarly sai.c handles COMP_TRIGGER_PAUSE and
COMP_TRIGGER_STOP identically. This patch joins those flows.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
mm_pm_context_save() and mm_pm_context_restore() are never used,
remove them.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
.dma_pm_context_store and .dma_pm_context_restore DMA operations are
never used, remove them.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
.pm_context_store and .pm_context_restore DAI operations are never
used, remove them.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
COMP_TRIGGER_* values are internal to SOF, they aren't a part of an
API, their numeric values are unimportant. Convert them to an enum to
make removing deprecated and adding new values easier.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
COMP_TRIGGER_SUSPEND and COMP_TRIGGER_RESUME are never issues, remove
them.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
In order to ease porting algorithm to SOF, it is convenient to have
stubs for some operating system function.
Those stubs are not meant to be called.
Signed-off-by: Lionel Koenig <lionelk@google.com>
All .tplg output files have been compared and are strictly identical
after the change.
The deprecation warnings were added more than one year ago in
https://github.com/alsa-project/alsa-lib/commits//706192341d1d0bbb906
Now that we just upgraded our Docker image to ALSA 1.2.6
(https://hub.docker.com/r/thesofproject/sof/tags) so #5153 can enable
topology v2, the volume of warnings has became unbearable. For instance
good luck trying to find the actual error messages for the build
failures of #5155 - they're totally drowned in these deprecation
warnings.
Signed-off-by: Marc Herbert <marc.herbert@intel.com>
We should gradually switch to ninja as a default.
ninja-build is apparently missing from build-essential
Signed-off-by: Marc Herbert <marc.herbert@intel.com>
The fewer macros, the better.
Commit 1758279623 ("perf: make trace part of perf counting
configurable") provided no specific rationale for using macros. It did
not explain why it passed some ignored arguments either - renamed
accordingly.
Signed-off-by: Marc Herbert <marc.herbert@intel.com>
1.Default support 1ms period capture pipeline to update host position
more precisely.
2.Revise pipeline 1 to playback and pipeline 4 to capture in comment.
Signed-off-by: YC Hung <yc.hung@mediatek.com>
Marc Herbert