Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Howard Mitchell <hm@hmbedded.co.uk>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Gordon Garrity <gordon.garrity@gmail.com>
Subject: Re: pcm512x driver: Mixer control naming issue
Date: Mon, 16 Mar 2015 11:11:12 +0100	[thread overview]
Message-ID: <s5hoant45hb.wl-tiwai@suse.de> (raw)
In-Reply-To: <5506A69B.1010601@hmbedded.co.uk>

At Mon, 16 Mar 2015 09:47:07 +0000,
Howard Mitchell wrote:
> 
> On 16/03/15 07:47, Takashi Iwai wrote:
> > At Sun, 15 Mar 2015 22:28:01 +0000,
> > Howard Mitchell wrote:
> >> On 13/03/15 18:27, Mark Brown wrote:
> >>> On Fri, Mar 13, 2015 at 12:41:05PM +0000, Howard Mitchell wrote:
> >>>
> >>>> Boost Volume) provides a boost of +0.8dB. The hardware reset value of both
> >>>> of these gain controls is 0dB, however, in the Raspbian distribution
> >>>> 'Playback Volume' is being defaulted to -6dB.
> >>>>    * Either change the names of these controls to something that's not
> >>>>      affected by the alsa restore mechanism,
> >>> You say "these controls" but it seems like only "Playback Volume" has
> >>> a problem?  My first suggestion would be to define "Analog" or
> >>> "Analogue" as a prefix in ControlNames and then use that, that would
> >>> avoid confusing applications while still fittig in with the naming
> >>> convention.
> >> Yes you are correct that it's only "Playback Volume" that is causing a
> >> problem. However, I included "Playback Boost Volume" as it also provides
> >> a selection of analogue gain so I think it should be treated similarly
> >> for consistency.
> > Did you read Documentation/sound/alsa/ControlNames.txt?
> > It shows why "Playback Volume" is taken in that way while "Playback
> > Boost Volume" not.  Namely, the latter implies a volume control named
> > "Playback Boost" which is applied generically -- i.e. the direction is
> > unknown or applied to both playback and capture.
> Sorry, what I meant by "treated similarly for consistency" is that 
> whatever solution is decided upon to fix the issue with "Playback 
> Volume" should also be applied to "Playback Boost Volume".
> 
> Your comment about the direction being unknown for "Playback Boost 
> Volume" is interesting though as when running alsamixer I find that 
> "Playback Volume" is also listed as a capture control. Neither makes 
> sense of course as this device does not have a capture path.

Congrats, you hit a bug in alsa-lib simple mixer layer.
Feel free to submit a fix patch :)


Takashi

  reply	other threads:[~2015-03-16 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5500DE5B.2020401@hmbedded.co.uk>
2015-03-13 12:41 ` pcm512x driver: Mixer control naming issue Howard Mitchell
2015-03-13 18:27   ` Mark Brown
2015-03-15 22:28     ` Howard Mitchell
2015-03-16  7:47       ` Takashi Iwai
2015-03-16  9:47         ` Howard Mitchell
2015-03-16 10:11           ` Takashi Iwai [this message]
2015-03-16 11:38       ` Mark Brown
2015-03-16 11:59         ` Takashi Iwai
2015-03-16 17:37         ` Howard Mitchell
2015-03-17 17:23           ` Mark Brown

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=s5hoant45hb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=gordon.garrity@gmail.com \
    --cc=hm@hmbedded.co.uk \
    /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