At present, some options for software parameters have actual effects in
cases neither mmap operation nor timer-based scheduling model is used.
For mmap operation, backward compatibility to aplay(1) is lost.
This commit adds descriptions about it.
Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
sound devices.
.TP
+.I \-A, \-\-avail\-min
+This option indicates threshold to wake up blocked process in a unit of
+audio data frame. Against aplay(1) implementation, this option has no effect
+with
+.I \-\-mmap
+option as well as
+.I timer
+of
+.I \-\-sched\-model
+option.
+
+.TP
+.I \-R, \-\-start\-delay
+This option indicates threshold to start prepared PCM substream in a unit of
+audio data frame. Against aplay(1) implementation, this option has no effect
+with
+.I \-\-mmap
+option as well as
+.I timer
+of
+.I \-\-sched\-model
+option.
+
+.TP
+.I \-T, \-\-stop\-delay
+This option indicates threshold to stop running PCM substream in a unit of
+audio data frame. Against aplay(1) implementation, this option has no effect
+with
+.I \-\-mmap
+option as well as
+.I timer
+of
+.I \-\-sched\-model
+option.
+
+.TP
.I \-\-max\-file\-time=#
This option is unsupported. In aplay(1) implementation, the option has an
effect for capture transmission to save files up to the same number of data