Skip to content

Conversation

@tmleman
Copy link
Contributor

@tmleman tmleman commented Jul 28, 2025

This patch introduces the Google RTC Audio Processing component into the PTL configuration for the SOF firmware. The component is added as a loadable module (m).

Changes:

  • Added CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m to enable Google RTC Audio Processing.
  • Included CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y for mock testing support.

@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch 2 times, most recently from 8b762e7 to 369ad4a Compare August 6, 2025 12:33
Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

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

Nice to see TWB being enabled for more CI testing.

@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch from 73acee1 to 8980eb1 Compare August 8, 2025 19:16
@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch from 8980eb1 to be014ea Compare August 27, 2025 13:42
Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

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

LGTM

@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch from be014ea to e23f9b1 Compare September 17, 2025 07:51
Copy link
Collaborator

@lyakh lyakh left a comment

Choose a reason for hiding this comment

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

this looks like a debugging PR mostly, not for upstreaming? Should we modify the title to indicate that? "[DEBUG][DNM]" or similar? I'll add a "DNM" label to it to help indicate, that this isn't for merging

@lyakh lyakh added the DNM Do Not Merge tag label Sep 18, 2025
@tmleman tmleman changed the title boards: ptl: add Google RTC Audio Processing to PTL configuration [WIP] boards: ptl: add Google RTC Audio Processing to PTL configuration Sep 18, 2025
@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch from b37bb25 to d927de5 Compare September 18, 2025 11:46
@tmleman tmleman removed the DNM Do Not Merge tag label Sep 18, 2025
@tmleman tmleman changed the title [WIP] boards: ptl: add Google RTC Audio Processing to PTL configuration boards: ptl: add Google RTC Audio Processing to PTL configuration Sep 18, 2025
@tmleman tmleman marked this pull request as ready for review September 18, 2025 11:49
Copilot AI review requested due to automatic review settings September 18, 2025 11:49
Copy link

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

This PR adds Google RTC Audio Processing component support to the PTL configuration and includes null pointer validation improvements in the audio host and copier modules.

  • Added Google RTC Audio Processing as a loadable module with mock testing support to PTL board configuration
  • Enhanced null pointer validation in host audio processing functions
  • Added converter function pointer validation in the copier module to prevent crashes

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
app/boards/intel_adsp_ace30_ptl.conf Enables Google RTC Audio Processing component and mock support
src/audio/host-zephyr.c Adds null check for local_buffer to prevent errors
src/audio/host-legacy.c Adds null check for local_buffer to prevent errors
src/audio/copier/copier.c Adds converter function pointer validation to prevent NULL dereference

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.


# SOF / audio modules / mocks
# This mock is part of official sof-bin releases because the CI that
# tests it can't use extra CONFIGs. See #9410, #8722 and #9386
Copy link

Copilot AI Sep 18, 2025

Choose a reason for hiding this comment

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

The comment on line 19 contains 'CONFIGs' which should be 'CONFIG options' or 'configuration options' for clarity and grammatical correctness.

Suggested change
# tests it can't use extra CONFIGs. See #9410, #8722 and #9386
# tests it can't use extra configuration options. See #9410, #8722 and #9386

Copilot uses AI. Check for mistakes.
@tmleman
Copy link
Contributor Author

tmleman commented Sep 18, 2025

this looks like a debugging PR mostly, not for upstreaming? Should we modify the title to indicate that? "[DEBUG][DNM]" or similar? I'll add a "DNM" label to it to help indicate, that this isn't for merging

I think it was in DRAFT to avoid merging, but I should have added something in the title for better clarity.

@tmleman tmleman requested review from lgirdwood and lyakh September 18, 2025 12:01
@tmleman tmleman force-pushed the topic/upstream/pr/intel/adsp/ptl/google_rtc branch 2 times, most recently from 15edda6 to 8ec2219 Compare September 22, 2025 07:12
Add NULL pointer check after calling `comp_dev_get_first_data_consumer`
and `comp_dev_get_first_data_producer` functions in host_common_params.

These functions can return NULL if no appropriate buffer is found in the
component's connection list. Without this check, a NULL pointer would be
assigned to hd->local_buffer and could cause crashes in subsequent
operations that assume a valid buffer pointer.

The error handling returns -EINVAL and logs an appropriate error message
to help with debugging pipeline configuration issues.

Signed-off-by: Tomasz Leman <tomasz.m.leman@intel.com>
This patch introduces the Google RTC Audio Processing component into the
PTL configuration for the SOF firmware. The component is added as a
loadable module (`m`).

**Changes:**
- Added `CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m` to enable Google RTC
  Audio Processing.
- Included `CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y` for mock testing
  support.

Signed-off-by: Tomasz Leman <tomasz.m.leman@intel.com>
Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

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

@tmleman I think we need the 1st patch in v2.14 and an open on the second part now.

# This mock is part of official sof-bin releases because the CI that
# tests it can't use extra CONFIGs. See #9410, #8722 and #9386
CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=m
CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=y
Copy link
Member

Choose a reason for hiding this comment

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

@tmleman fwiw @kv2019i has been updating the configs to make them scale better with different targets. @kv2019i is this part good to merge ?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@tmleman @lgirdwood It's ok here if this is truly PTL specific. If it's a setting we want for all newer platforms, the it should go to the new common Intel board config file I added to main.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@kv2019i @lgirdwood Before adding the module on the platform, it must be tested. Ultimately, we won't be enabling this module on LNL either.
When the module is ready for WCL and NVL, we can consider moving it to a generic Kconfig. That's my opinion.

Copy link
Collaborator

@kv2019i kv2019i left a comment

Choose a reason for hiding this comment

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

+1 with the assumption this specifically needs to be PTL specific.

@tmleman
Copy link
Contributor Author

tmleman commented Sep 23, 2025

SOFCI TEST

@lgirdwood lgirdwood merged commit c1b673e into thesofproject:main Sep 30, 2025
37 of 45 checks passed
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