From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.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 15:38:25 +0530 [thread overview]
Message-ID: <505AEB19.7080205@st.com> (raw)
In-Reply-To: <505AE8C6.3040001@ti.com>
Hello Peter
On 9/20/2012 3:28 PM, Peter Ujfalusi wrote:
> On 09/20/2012 10:56 AM, Rajeev kumar wrote:
>> Hello Mark,
>>
>> We have three volume control in audio codec.
>> 1. Master volume: control both left and right channel volume
>> 2. left volume: control left channel vol
>> 3. right volume: control right channel vol.
>>
>> So we can provide interfaces for all volume control to the user. Please
>> find below the control I can provide to the user space
>>
>> case 1:
>> 1. Provide master volume control
>> 2. Provide Left channel volume control.
>> 3. Provide Right channel volume control.
>>
>> case 2:
>>
>> 1. Provide master volume control
>> 2. Instead of providing separate control for left and right channel,
>> combined it and provide a single control to user space. so that left and right
>> volume is always in sync.
>
> 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?
In case user wants a separate left/right volume control then how this
setting is going to help.
Best Rgds
~Rajeev
next prev parent reply other threads:[~2012-09-20 10:08 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 [this message]
2012-09-20 10:19 ` Peter Ujfalusi
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=505AEB19.7080205@st.com \
--to=rajeev-dlh.kumar@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@ti.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).