From: Tanu Kaskinen Date: Thu, 26 Jun 2014 10:30:25 +0000 (+0300) Subject: ucm: Document PlaybackPCMIsDummy and CapturePCMIsDummy values X-Git-Tag: android-x86-9.0-r1~787 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=7a748af4db17cb0b26d19e5f9939d277128ec94b;p=android-x86%2Fexternal-alsa-lib.git ucm: Document PlaybackPCMIsDummy and CapturePCMIsDummy values At least PulseAudio needs special handling for dummy devices. To allow that to happen automatically, the UCM configuration should contain the information about which PCMs are dummy. Signed-off-by: Tanu Kaskinen Acked-by: Liam Girdwood Signed-off-by: Takashi Iwai --- diff --git a/include/use-case.h b/include/use-case.h index 4e132491..f30168f8 100644 --- a/include/use-case.h +++ b/include/use-case.h @@ -258,7 +258,17 @@ int snd_use_case_get_list(snd_use_case_mgr_t *uc_mgr, * Recommended names for values: * TQ - Tone Quality * PlaybackPCM - full PCM playback device name + * PlaybackPCMIsDummy - Valid values: "yes" and "no". If set to "yes", the + * PCM named by the PlaybackPCM value is a dummy device, + * meaning that opening it enables an audio path in the + * hardware, but writing to the PCM device has no + * effect. * CapturePCM - full PCM capture device name + * CapturePCMIsDummy - Valid values: "yes" and "no". If set to "yes", the + * PCM named by the CapturePCM value is a dummy device, + * meaning that opening it enables an audio path in the + * hardware, but reading from the PCM device has no + * effect. * PlaybackRate - playback device sample rate * PlaybackChannels - playback device channel count * PlaybackCTL - playback control device name