Skip to content

boards: nvl: add Google RTC Audio Processing to NVL configs#10832

Open
wjablon1 wants to merge 1 commit into
thesofproject:mainfrom
wjablon1:nvl_aec_support
Open

boards: nvl: add Google RTC Audio Processing to NVL configs#10832
wjablon1 wants to merge 1 commit into
thesofproject:mainfrom
wjablon1:nvl_aec_support

Conversation

@wjablon1
Copy link
Copy Markdown
Contributor

@wjablon1 wjablon1 commented Jun 2, 2026

Enable the Google RTC Audio Processing component as a loadable module for NVL and NVL-S boards.

This change adds CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m and CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y to both board config files.

(This is to just unblock some test cases on NVL platforms)

Enable the Google RTC Audio Processing component as a loadable module
for NVL and NVL-S boards.

This change adds CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m and
CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y to both board config files.

Signed-off-by: Wojciech Jablonski <wojciech.jablonski@intel.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Enables the Google RTC Audio Processing component for Intel ADSP ACE40 NVL/NVL-S board builds by turning it on as a loadable module and forcing the mock implementation to unblock CI/test execution on these platforms.

Changes:

  • Add CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m to NVL and NVL-S board config files.
  • Add CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y (with explanatory comment) to ensure builds/tests don’t depend on extra CI-provided Kconfig.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
app/boards/intel_adsp_ace40_nvl.conf Enable Google RTC Audio Processing as a module and force mock for NVL.
app/boards/intel_adsp_ace40_nvls.conf Enable Google RTC Audio Processing as a module and force mock for NVL-S.

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.

4 participants