Repository navigation
[BUG] glitch in test 02_00_TestPtpSimpleLoopback48000Hz24b32b8ch #4076
Description
Describe the bug
Glitch was found in test 02_00_TestPtpSimpleLoopback48000Hz24b32b8ch
Topology
pipe_plb
+------------------------------+
|-------+ +------+ +-----+ | +----+
|| Host +-->+Buffer+-->+ Dai +---->+SSPX|
|-------+ +------+ +-----+ | +----+
+------------------------------+ | |
| |
pipe_cap | |
+------------------------------+ | |
|-------+ +------+ +-----+ | +----+
|| Host +<--+Buffer+<--+ Dai +---->+SSPX|
|-------+ +------+ +-----+ | +----+
+------------------------------+
To Reproduce
Run test with Diagnostic driver 02_00_TestPtpSimpleLoopback48000Hz24b32b8ch
With options --playback-iterations=75
Reproduction Rate
1/75
Environment
- Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
- SOF BRANCH: main HASH: dc0ab8a
- Name of the platform(s) on which the bug is observed.
- Platform: ICL RVP
- Test environment:
BRANCH: master HASH: 180819001ee5c678ee2b6a53b4931c605a14e89c
Screenshots or console output
Activity
lgirdwood commentedon Apr 27, 2021
@wszypelt @zrombel I didn't know we supported the same buffer for host DMA and DAI DMA ? I thought the simplest would be the passthrough volume that places a volume in the middle to make sure we dont use the same buffer for host and DAI DMA ?
zrombel commentedon Apr 27, 2021
This image can be a little bit confusing as "Host plb" and "Host cap" component are a part of pipelines (test documentation needs a fix). Regarding buffers: buffers shown on topology are buffers that are explicitly created by test logic by IPC "TplgBuffNew" but as far as I know one another buffer is being created implicitly by FW for data from host DMA - those buffers are not included in tests topology drawings. Please correct me if I'm wrong.
lgirdwood commentedon May 13, 2021
There is a lot of very similar loopback test failures using different audio pipelines with different processing options now marked with "duplicate" label.
All these tests have loopback in common so this simple example should be solved first as it's test case architecture is shared with the other more complex examples. Once this is solved , then the others can be retested and closed/updated as necessary.
wszypelt commentedon Oct 13, 2022
No longer reproduced