Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App: Boards: Set CONFIG_COMP_DRC=y for LNL platform #8963

Merged
merged 1 commit into from
Mar 19, 2024

Conversation

singalsu
Copy link
Collaborator

The DRC component was not included to build. This change avoids error and DSP panic in topology load.

The DRC component was not included to build. This change
avoids error and DSP panic in topology load.

Signed-off-by: Seppo Ingalsuo <seppo.ingalsuo@linux.intel.com>
@singalsu singalsu changed the title App: Boards: Set COMP_COMP_DRC=y for LNL platform App: Boards: Set CONFIG_COMP_DRC=y for LNL platform Mar 19, 2024
@singalsu singalsu marked this pull request as ready for review March 19, 2024 10:04
CONFIG_COMP_SRC_IPC4_FULL_MATRIX=y
CONFIG_COMP_DRC=y
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively should this be a library @singalsu ?

I thought this was the direction of travel for all processing components?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea how to do it and if it's in usable state, I saw there were problems with IIR as test. This is a fix for new platform failure #8961, so if this works I'd prefer a quick merge and improve to library later. Also better to experiment new things in mature platform like MTL.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@plbossart we are not there yet @lyakh correct me if I'm wrong

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't @lgirdwood say that we would only test volume as separate components though? Maybe I am confused on timelines, but do we agree that at some point all those processing should come as libraries?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@plbossart you mean as loadable libraries / modules? @kv2019i is right - in principle it's all there and working, there are just a couple of "temporary minor issues," e.g. ATM it's only working with open-source toolchains like the Zephyr one, not with the Cadence Xplorer based one...

Copy link
Member

@plbossart plbossart Mar 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Humm, then the stated goal of testing volume components only as libraries is not realistic until all dependencies are handled. Clearly the use of the Cadence toolchain is a key requirement, we don't release anything based on open-source toolchains.

CONFIG_COMP_SRC_IPC4_FULL_MATRIX=y
CONFIG_COMP_DRC=y
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@plbossart we are not there yet @lyakh correct me if I'm wrong

@fredoh9
Copy link
Contributor

fredoh9 commented Mar 19, 2024

I'm able to test with this PR. playback tests are working fine!

Copy link
Member

@plbossart plbossart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no objection to merge to unlock daily tests, but I'd like clarity on the directions for processing components (built-in with Kconfig or libraries) and by when. Thanks!

@kv2019i kv2019i merged commit 51bd1ae into thesofproject:main Mar 19, 2024
41 of 43 checks passed
@singalsu singalsu deleted the lnl_enable_drc_kconfig branch August 21, 2024 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants