alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Rajeev kumar <rajeev-dlh.kumar@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Audio codec volume control
Date: Thu, 20 Sep 2012 13:19:01 +0300	[thread overview]
Message-ID: <505AED95.20400@ti.com> (raw)
In-Reply-To: <505AEB19.7080205@st.com>

On 09/20/2012 01:08 PM, Rajeev kumar wrote:
>> case 3:
>> 1. Provide master volume control
>> 2. stereo volume control for the left/right channel
>>
> 
> You mean to say
> Left and Right should be a single stereo control which can be provided with
> SOC_DOUBLE. Actually case 2 corresponds to the same setting which you are
> suggesting.
> 
> But why this is better option?

You have less controls for the codec -> easier for users.
Users still can adjust the left/right differently if they want.

> In case user wants a separate left/right volume control then how this setting
> is going to help.

In most cases you change both left/right channel:
amixer sset 'PCM' 8 # left/right volume is 8

but users can set different volume per channel:
amixer sset 'PCM' 8,1 # left volume is 8, right is 1

it is better than:
amixer sset 'PCM Left' 8 # left volume is 8
amixer sset 'PCM Right' 8 # left volume is 8

or
amixer sset 'PCM Left' 8 # left volume is 8
amixer sset 'PCM Right' 1 # left volume is 1

-- 
Péter

  reply	other threads:[~2012-09-20 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  7:56 Audio codec volume control Rajeev kumar
2012-09-20  9:58 ` Peter Ujfalusi
2012-09-20 10:08   ` Rajeev kumar
2012-09-20 10:19     ` Peter Ujfalusi [this message]
2012-09-20 10:39       ` Rajeev kumar
2012-09-20 10:46         ` Peter Ujfalusi

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=505AED95.20400@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=rajeev-dlh.kumar@st.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;
as well as URLs for NNTP newsgroup(s).