From: "naveen krishna ch" <naveenkrishna.ch@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, Steve Sakoman <steve@sakoman.com>
Subject: Re: Kcontrols for ASoC TWL4030 CODEC
Date: Thu, 20 Nov 2008 19:31:15 +0530 [thread overview]
Message-ID: <ef0d8a250811200601n5bcede89xb442dc26cb05fe8a@mail.gmail.com> (raw)
In-Reply-To: <20081120133644.GE4539@sirena.org.uk>
On Thu, Nov 20, 2008 at 7:06 PM, Mark Brown <broonie@sirena.org.uk> wrote:
> On Thu, Nov 20, 2008 at 06:12:56PM +0530, naveen krishna ch wrote:
>
> > static const struct snd_kcontrol_new twl4030_snd_controls[] = {
> > - SOC_DOUBLE_R("Master Playback Volume",
> > - TWL4030_REG_ARXL2PGA, TWL4030_REG_ARXR2PGA,
> > - 0, 127, 0),
> > - SOC_DOUBLE_R("Capture Volume",
> > - TWL4030_REG_ATXL1PGA, TWL4030_REG_ATXR1PGA,
> > - 0, 127, 0),
> > +
> > + /* Master Playback Volume Controls */
> > + SOC_DOUBLE_R("Master PLayback Course Gain",
> > + TWL4030_REG_ARXL2PGA, TWL4030_REG_ARXR2PGA,
> > + 6, 3, 0),
> > +
>
> Please see the comments I made in response to your original posting -
> there look to be problems with your indentation here and your control
> names should conform to the ALSA control naming standard in:
Sorry i could not solve the issue with the indentation i have attached the
patch file.
>
>
> Documentation/sound/alsa/ControlNames.txt
The standard names in the documentation does not gives the exact details of
the CODEC's feature so i used a part of the CODEC pin name to avoid
confusion at later stages.
Course and Fine controls are feature given by the CODEC so distinguish them
i named them against the features.
There is an internal and external speaker facility i name d them against
that.
However i will re submit the patch with some modifications in names.
--
Thanks,
(: Naveen Krishna Ch :)
next prev parent reply other threads:[~2008-11-20 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 12:42 Kcontrols for ASoC TWL4030 CODEC naveen krishna ch
2008-11-20 13:36 ` Mark Brown
2008-11-20 14:01 ` naveen krishna ch [this message]
2008-11-20 14:04 ` 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=ef0d8a250811200601n5bcede89xb442dc26cb05fe8a@mail.gmail.com \
--to=naveenkrishna.ch@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=steve@sakoman.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