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

config: enable PIPELINE_2_0 for IPC4 fuzz testing #9677

Conversation

tmleman
Copy link
Contributor

@tmleman tmleman commented Nov 22, 2024

This patch enables the PIPELINE_2_0 configuration for IPC4 fuzz testing by updating the fuzz_IPC4_features.conf file. The PIPELINE_2_0 flag is required for certain new features, such as DP_SCHEDULER, and improves code coverage for the IPC4 configuration.

The change has been tested locally and does not introduce any regressions.

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 tmleman force-pushed the topic/upstream/pr/ipc4/fuzzing/add_ppl_20 branch from 84a3df8 to c672453 Compare November 25, 2024 13:22
@tmleman tmleman marked this pull request as ready for review November 25, 2024 13:24
This patch enables the PIPELINE_2_0 configuration for IPC4 fuzz testing
by updating the fuzz_IPC4_features.conf file. The PIPELINE_2_0 flag is
required for certain new features, such as DP_SCHEDULER, and improves
code coverage for the IPC4 configuration.

This option is enabled on all platforms using IPC4, with the exception
of those based on CAVS, which are not used in production. The change has
been tested locally and does not introduce any regressions.

Signed-off-by: Tomasz Leman <[email protected]>
@cujomalainey
Copy link
Contributor

Failing checks unrelated, merging

@cujomalainey cujomalainey merged commit 4531cfa into thesofproject:main Nov 25, 2024
44 of 47 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.

3 participants