Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] ALSA: Update control names documentation
Date: Mon, 20 Oct 2014 15:38:04 +0200	[thread overview]
Message-ID: <s5hd29mlv43.wl-tiwai@suse.de> (raw)
In-Reply-To: <1413808689-4175-1-git-send-email-david.henningsson@canonical.com>

At Mon, 20 Oct 2014 14:38:09 +0200,
David Henningsson wrote:
> 
> This document was not really up-to-date. Add recent additions to this
> standard - based on what the HDA driver currently does, which is some
> kind of a de facto standard.
> 
> Signed-off-by: David Henningsson <david.henningsson@canonical.com>

Looks god to me as a start.  Applied to for-next branch now.


thanks,

Takashi


> ---
>  Documentation/sound/alsa/ControlNames.txt | 32 ++++++++++++++++++++++++++-----
>  1 file changed, 27 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/sound/alsa/ControlNames.txt b/Documentation/sound/alsa/ControlNames.txt
> index fea65bb..79a6127 100644
> --- a/Documentation/sound/alsa/ControlNames.txt
> +++ b/Documentation/sound/alsa/ControlNames.txt
> @@ -1,6 +1,6 @@
>  This document describes standard names of mixer controls.
>  
> -Syntax: SOURCE [DIRECTION] FUNCTION
> +Syntax: [LOCATION] SOURCE [CHANNEL] [DIRECTION] FUNCTION
>  
>  DIRECTION:
>    <nothing>	(both directions)
> @@ -14,12 +14,29 @@ FUNCTION:
>    Volume
>    Route		(route control, hardware specific)
>  
> +CHANNEL:
> +  <nothing>     (channel independent, or applies to all channels)
> +  Front
> +  Surround      (rear left/right in 4.0/5.1 surround)
> +  CLFE
> +  Center
> +  LFE
> +  Side          (side left/right for 7.1 surround)
> +
> +LOCATION:       (physical location of source)
> +  Front
> +  Rear
> +  Dock          (docking station)
> +  Internal
> +
>  SOURCE:
>    Master
>    Master Mono
>    Hardware Master
>    Speaker	(internal speaker)
> +  Bass Speaker	(internal LFE speaker)
>    Headphone
> +  Line Out
>    Beep		(beep generator)
>    Phone
>    Phone Input
> @@ -27,14 +44,14 @@ SOURCE:
>    Synth
>    FM
>    Mic
> -  Line
> +  Headset Mic	(mic part of combined headset jack - 4-pin headphone + mic)
> +  Headphone Mic	(mic part of either/or - 3-pin headphone or mic)
> +  Line		(input only, use "Line Out" for output)
>    CD
>    Video
>    Zoom Video
>    Aux
>    PCM
> -  PCM Front
> -  PCM Rear
>    PCM Pan
>    Loopback
>    Analog Loopback	(D/A -> A/D loopback)
> @@ -47,8 +64,13 @@ SOURCE:
>    Music
>    I2S
>    IEC958
> +  HDMI
> +  SPDIF		(output only)
> +  SPDIF In
> +  Digital In
> +  HDMI/DP	(either HDMI or DisplayPort)
>  
> -Exceptions:
> +Exceptions (deprecated):
>    [Digital] Capture Source
>    [Digital] Capture Switch	(aka input gain switch)
>    [Digital] Capture Volume	(aka input gain volume)
> -- 
> 1.9.1
> 

  reply	other threads:[~2014-10-20 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 12:38 [PATCH] ALSA: Update control names documentation David Henningsson
2014-10-20 13:38 ` Takashi Iwai [this message]
2014-10-20 23:46 ` Raymond Yau
2014-10-21  3:38   ` David Henningsson

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=s5hd29mlv43.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=david.henningsson@canonical.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