Skip to content

Commit 84dcefd

Browse files
committed
check-alsabat.sh: explain that we run two alsabat instances
This threw me off. Also add warning that https://manpages.org/alsabat is incomplete and never tells that it is possible to use two separate alsabat instances, nor how to invoke these (answer: omit -P or -C) Signed-off-by: Marc Herbert <marc.herbert@intel.com>
1 parent a21c389 commit 84dcefd

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

test-case/check-alsabat.sh

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,24 @@
22

33
##
44
## Case Name: check alsabat
5+
##
56
## Preconditions:
67
## This test case requires physical loopback between playback and capture.
78
## playback <=====> capture
89
## nocodec : no need to use hw loopback cable, It support DSP loopback by quirk
10+
##
911
## Description:
10-
## run alsabat test on the specified pipelines
12+
## Run two alsabat instances concurrently, one on each specified PCM: playback
13+
## and capture.
14+
##
15+
## Warning: as of January 2024, "man alsabat" is incomplete and
16+
## documents only the "single instance" mode where a single alsabat
17+
## process performs both playback and capture.
18+
##
1119
## Case step:
1220
## 1. Specify the pcm IDs for playback and catpure
1321
## 3. run alsabat test
22+
##
1423
## Expect result:
1524
## The return value of alsabat is 0
1625
##

0 commit comments

Comments
 (0)