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

[FEATURE] test all possible number of channels #1001

Open
fredoh9 opened this issue Feb 2, 2023 · 0 comments
Open

[FEATURE] test all possible number of channels #1001

fredoh9 opened this issue Feb 2, 2023 · 0 comments
Labels
P2 Critical bugs or normal features type:enhancement New framework feature or request type:test coverage gap This requires a new test case, not just fixing one

Comments

@fredoh9
Copy link
Collaborator

fredoh9 commented Feb 2, 2023

Currently all of topologies for the devices in SOF CI are either ch_min=2;ch_max=2 or ch_min=4;ch_max=4.
We will need to support multi channel audio up to 8 channels,

We will see the pipelines for 7.1 multi channel or 5.1 multi channel.

  • 7.1 multi channel : ch_min=2;ch_max=8
  • 5.1 multi channel : ch_min=2;ch_max=6

Then we need to try all supported channels from min to max.

TODO: Need to clarify the requirement. When a pipeline supports 8 channels, ch_min=2;ch_max=8,

  • should we try any integer number between min and max? i.e 2,3,4,5,6,7,8
  • or known/popular channel numbers? i.e 2,6,8
  • or only with even numbers between min and max? i.e 2,4,6,8
@marc-hb marc-hb changed the title [FEATURE] all possible number of channels test support [FEATURE] test all possible number of channels Jun 22, 2023
@marc-hb marc-hb added type:enhancement New framework feature or request P2 Critical bugs or normal features type:test coverage gap This requires a new test case, not just fixing one labels Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Critical bugs or normal features type:enhancement New framework feature or request type:test coverage gap This requires a new test case, not just fixing one
Projects
None yet
Development

No branches or pull requests

2 participants