You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Separation of volume control and PCM conversion functionalities #1610
PCM format conversion and volume control are independent audio signal processing actions. To have better functional separation of components the 2 functionalities of existing Volume component shall be separated. Low power use cases call for for FW components footprint optimization as well.
Requested change is to create 2 separate components : PCM converter and Volume control and implementation of PCM conversion functions as a library functions (generic & optimized for HiFi co-processor) that can be used i.e. by Keyphrase Detection component.
@lbetlej these were historically converged since volume control would be on most pipelines and this would give any PCM format conversion needed downstream for free (and avoiding the need for an extra copy), but you are right this does not provide a library for other users (which we could use internally by volume). I would still keep volume performing PCM format conversion though.
I think we can reduce footprint by using Kconfig for supported volume PCM formats.
Activity
lgirdwood commentedon Jul 4, 2019
@lbetlej these were historically converged since volume control would be on most pipelines and this would give any PCM format conversion needed downstream for free (and avoiding the need for an extra copy), but you are right this does not provide a library for other users (which we could use internally by volume). I would still keep volume performing PCM format conversion though.
I think we can reduce footprint by using Kconfig for supported volume PCM formats.
ktrzcinx commentedon Apr 15, 2020
Done in #2029