From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
David@alsa-project.org,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
linux-kernel <linux-kernel@vger.kernel.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 18:49:58 +0530 [thread overview]
Message-ID: <1318943998.13721.42.camel@matrix> (raw)
In-Reply-To: <20111018125519.GB18713@sirena.org.uk>
On Tue, 2011-10-18 at 13:55 +0100, Mark Brown wrote:
> On Tue, Oct 18, 2011 at 06:30:28PM +0530, Ashish Chavan wrote:
>
> > > Eh? One is a Volume, the other is a Switch. Note that alsamixer does
> > > render the two stacked on top of each other in the UI.
>
> > Yes, I guessed that earlier. Anyways I generally don't rely on alsamixer
> > and use amixer whereever possible. In amixer also, it shows only one
> > control, the one that I add first. If I change "Mic" to some thing else
> > like "MicM" or "Mic Mute", then it shows both controls.
>
> Check again, amixer also merges controls.
>
Yes, you are right.
> > BTW does amixer version have any significance here? I know my alsa-utils
> > are quite old (1.0.14)
>
> That's spectacularly old, I guess it's possible it's buggy.
>
I see, thanks. I will update it to my earliest convenience. As of now, I
will go forward in submitting the patches.
prev parent reply other threads:[~2011-10-18 13:08 UTC|newest]
Thread overview: 11+ 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-17 21:42 ` [alsa-devel] " 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
2011-10-18 12:31 ` [alsa-devel] " Mark Brown
2011-10-18 13:00 ` Ashish Chavan
2011-10-18 12:55 ` Mark Brown
2011-10-18 12:55 ` [alsa-devel] " Mark Brown
2011-10-18 13:19 ` Ashish Chavan [this message]
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=1318943998.13721.42.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.