From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
David@alsa-project.org, Chen <david.chen@diasemi.com>,
lrg <lrg@ti.com>
Subject: Re: [PATCH v4 3/7] ASoC: da7210: Add support for mute and zero cross controls
Date: Tue, 18 Oct 2011 17:59:03 +0530 [thread overview]
Message-ID: <1318940943.13721.25.camel@matrix> (raw)
In-Reply-To: <20111018120841.GA28501@opensource.wolfsonmicro.com>
On Tue, 2011-10-18 at 13:08 +0100, Mark Brown wrote:
> On Tue, Oct 18, 2011 at 05:19:08PM +0530, Ashish Chavan wrote:
>
> > SOC_DOUBLE_R("Mic Capture Switch", ...),
> > SOC_SINGLE("Aux2 Capture Switch", ...),
>
> > Now I have realized that this may cause a naming conflict with my
> > "mic_aux_inpga" patch, which I am going to submit after DAPM issues get
> > sorted. In "mic aux inpga" patch there are controls for Mic and Aux2
> > volume control,
>
> > SOC_DOUBLE_R_TLV("Mic Capture Volume", ...),
> > SOC_SINGLE_TLV("Aux2 Capture Volume", ...),
>
> > As per my view, "Mic Capture Volume" is correct name for Mic volume
> > control and we need to change name for Mic mute control. Do you agree?
> > If yes, any suggestion for the name of Mic mute control?
>
> I don't see any conflict in the above?
>
If I add these two, alsamixer and amixer shows only one of them (one
which is added first). Is that fine?
I guess the token here is only "Mic" and "Aux2".
next prev parent reply other threads:[~2011-10-18 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 9:23 [PATCH v4 3/7] ASoC: da7210: Add support for mute and zero cross controls Ashish Chavan
2011-10-17 21:42 ` Mark Brown
2011-10-18 11:49 ` Ashish Chavan
2011-10-18 12:08 ` [alsa-devel] " Mark Brown
2011-10-18 12:29 ` Ashish Chavan [this message]
2011-10-18 12:31 ` Mark Brown
2011-10-18 13:00 ` Ashish Chavan
2011-10-18 12:55 ` Mark Brown
2011-10-18 13:19 ` Ashish Chavan
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=1318940943.13721.25.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=David@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david.chen@diasemi.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@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).