From: Takashi Iwai <tiwai@suse.de>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Felipe Tonello <eu@felipetonello.com>,
Liam Girdwood <liam.r.girdwood@intel.com>
Subject: Re: [PATCH] ucm: Document PlaybackPCMIsDummy and CapturePCMIsDummy values
Date: Fri, 27 Jun 2014 14:23:08 +0200 [thread overview]
Message-ID: <s5hwqc2tuc3.wl%tiwai@suse.de> (raw)
In-Reply-To: <1403778625-4608-1-git-send-email-tanu.kaskinen@linux.intel.com>
At Thu, 26 Jun 2014 13:30:25 +0300,
Tanu Kaskinen wrote:
>
> 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 <tanu.kaskinen@linux.intel.com>
Thanks, applied with Liam's ack.
Takashi
> ---
> include/use-case.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/use-case.h b/include/use-case.h
> index 4e13249..f30168f 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
> --
> 1.9.3
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
prev parent reply other threads:[~2014-06-27 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:30 [PATCH] ucm: Document PlaybackPCMIsDummy and CapturePCMIsDummy values Tanu Kaskinen
2014-06-26 12:49 ` Liam Girdwood
2014-06-27 12:23 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hwqc2tuc3.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=eu@felipetonello.com \
--cc=liam.r.girdwood@intel.com \
--cc=tanu.kaskinen@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox