Pierre-Louis Bossart
Pierre-Louis Bossart
The premise for multi-link support is that the first link will start the bank switch on all links, using hardware-based sync. This is currently implemented, but we still call wait_for_completion()...
in sound/soc/sof/pcm.c we have this ````c /* set wait time - TODO: come from topology */ substream->wait_time = 500; ```` Let's add a token for this.
Low-level hardware related restrictions/constraints don't belong in topology files. They should be set in platform-specific drivers. We should also clarify why the need for exposing period sizes in the topology.
This is the mirror of the SOF issue https://github.com/thesofproject/sof/issues/629 We need the ability to activate audio clocks independently either at boot or on-demand. This will require a dedicated kernel module...
We don't seem to handle the DRAIN trigger, which is potentially an issue to play short sounds or to deal with deep buffers. This probably has firmware implications. Note that...
This device has RT711 on link0, RT1316 on link3 and 2 PCH-attached DMICs. Add 3 configurations with no DMIC, 4 DMIC and 2 DMIC. For now no support for -pdm1.
**Describe the bug** when the firmware fails on a memory allocation, the error code is not provided to the host driver. Instead we see a useless "Unsupported operation requested". See...
**Is your feature request related to a problem? Please describe.** The nocodec topology exposes redundant intermediate copiers on the SSP input path ![sof-mtl-nocodec](https://github.com/thesofproject/sof/assets/1149035/f19461a0-5292-447f-a132-31b52cf4f500) ![Screenshot from 2024-03-20 18-04-54](https://github.com/thesofproject/sof/assets/1149035/e3b01d36-99a3-4165-9e8e-b084354a9251) **Describe the solution...
Reported initially by @bardliao All SoundWire topologies currently use S32_LE, which means all 32-bits of data will be pushed on the wire. The problem is that the default frame shape...
**Describe the bug** lots of warning messages for Device tree and Kconfig. Am I the only one that looks at build logs? **To Reproduce** ./sof/scripts/xtensa-build-zephyr.py --use-platform-subdir --key-type-subdir dbgkey -k ~/mtl_debug_private_key.pem...