-
Notifications
You must be signed in to change notification settings - Fork 349
boards: ptl: add Google RTC Audio Processing to PTL configuration #10140
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
boards: ptl: add Google RTC Audio Processing to PTL configuration #10140
Conversation
8b762e7 to
369ad4a
Compare
lgirdwood
left a comment
There was a problem hiding this 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.
73acee1 to
8980eb1
Compare
8980eb1 to
be014ea
Compare
lgirdwood
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
be014ea to
e23f9b1
Compare
lyakh
left a comment
There was a problem hiding this 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
b37bb25 to
d927de5
Compare
There was a problem hiding this 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 |
Copilot
AI
Sep 18, 2025
There was a problem hiding this comment.
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.
| # 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 |
I think it was in DRAFT to avoid merging, but I should have added something in the title for better clarity. |
15edda6 to
8ec2219
Compare
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>
lgirdwood
left a comment
There was a problem hiding this 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
kv2019i
left a comment
There was a problem hiding this 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.
|
SOFCI TEST |
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:
CONFIG_COMP_GOOGLE_RTC_AUDIO_PROCESSING=mto enable Google RTC Audio Processing.CONFIG_GOOGLE_RTC_AUDIO_PROCESSING_MOCK=yfor mock testing support.