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

topology2: google-rtc-aec: expose component core_id for override #8308

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

yongzhi1
Copy link
Contributor

@yongzhi1 yongzhi1 commented Oct 11, 2023

RTC AEC module is using DP and rest of echo ref pipeline is LL, and both can run on secondary cores.
In order to assign RTC_AEC DP alone on secondary core, add new macro GOOGLE_AEC_DP_CORE_ID.

@yongzhi1 yongzhi1 marked this pull request as draft October 11, 2023 15:31
@lgirdwood
Copy link
Member

@yongzhi1 I guess we need other PRs for FW and SW from @marcinszkudlinski and @ranj063 before we can merge ?

@yongzhi1
Copy link
Contributor Author

@yongzhi1 I guess we need other PRs for FW and SW from @marcinszkudlinski and @ranj063 before we can merge ?

Yes, that's right. The DP AEC support has dependency on #8403; thesofproject/linux#4664 and other fix.

@yongzhi1 yongzhi1 changed the title topology2: google-rtc-aec: use DP scheduler topology2: google-rtc-aec: expose component core_id for override Nov 1, 2023
@yongzhi1 yongzhi1 marked this pull request as ready for review November 1, 2023 17:07
@yongzhi1
Copy link
Contributor Author

yongzhi1 commented Nov 2, 2023

Update:

Fix the comment to avoid confusion.

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.

Thanks @yongzhi1 !

@@ -95,7 +95,10 @@ Define {
BT_PB_DAI_PIPELINE_SRC "copier.host.9.1"
BT_PB_PIPELINE_STREAM_NAME "dai-copier.SSP.10.1"
GOOGLE_RTC_AEC_SUPPORT 0
# assign core for AEC LL pipelines
GOOGLE_AEC_CORE_ID 0
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to run AEC as LL?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@marcinszkudlinski I think this is for the rest of the pipeline on which AEC is.

Copy link
Contributor Author

@yongzhi1 yongzhi1 Nov 3, 2023

Choose a reason for hiding this comment

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

yes, for example, as a test we can run echo ref related pipelines on core 2 (LL), and put RTC_AEC module (DP) alone on core 1:

Copy link
Member

Choose a reason for hiding this comment

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

ok, so comment is a little confusing. We should update it to say AEC is using DP and rest of pipeline is LL and both are on different cores.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ack, will update commit message as well as the PR description, thanks,

RTC_AEC module is using DP and rest of pipeline is LL and both can
run on different cores.

For the purpose to assign DP module individually on secondary core,
now add a new macro GOOGLE_AEC_DP_CORE_ID.

Signed-off-by: Yong Zhi <[email protected]>
@yongzhi1
Copy link
Contributor Author

yongzhi1 commented Nov 6, 2023

Update:
Improved commit description based on reviews.

@lgirdwood lgirdwood merged commit 49377e8 into thesofproject:main Nov 7, 2023
43 of 44 checks passed
@yongzhi1 yongzhi1 deleted the dp-aec branch November 7, 2023 14:54
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