From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: What is correct way to put conditional stuff in ASoC codec driver?
Date: Thu, 7 Jul 2011 08:49:34 -0700 [thread overview]
Message-ID: <20110707154933.GB16325@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1310039407.15931.195.camel@matrix>
On Thu, Jul 07, 2011 at 05:20:07PM +0530, Ashish Chavan wrote:
> On Wed, 2011-07-06 at 01:07 +0530, Mark Brown wrote:
> > No, that's not a user visible control that's part of the internal DAPM
> > power management stuff. You're looking for struct snd_kcontrol_new
> > stuff.
> Oh, that's correct. You may be suggesting something similar to what is
> done in sound/soc/codecs/wm8985.c for "Equalizer Function", i.e. using
> SOC_xxx_EXT version for defining custom control and putting condition
> checks in respective "_put()" function.
Or just writing a control directly.
> > The state of another control is one example of a dynamic source of
> > information.
> Can you point me to any example that shows correct way to inquire
> state/value of a custom control? I guess snd_soc_get_xxx() functions
> need to be used here but I could find only handful of usages of these
> functions in entire sound/soc/codecs dir.
Those functions are used by the core for providing readback of the
controls to userspace. You need to provide them but your driver can use
whatever it likes to read its own state (providing it's tasteful), it
doesn't need to go through external APIs. Any driver with a custom
control will have an example of how it chooses to read its own state.
next prev parent reply other threads:[~2011-07-11 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 12:46 What is correct way to put conditional stuff in ASoC codec driver? Ashish Chavan
2011-06-30 16:37 ` Mark Brown
2011-07-01 8:33 ` Ashish Chavan
2011-07-01 16:17 ` Mark Brown
2011-07-04 6:56 ` Ashish Chavan
2011-07-04 22:34 ` Mark Brown
2011-07-05 14:25 ` Ashish Chavan
2011-07-05 19:37 ` Mark Brown
2011-07-07 11:50 ` Ashish Chavan
2011-07-07 15:49 ` Mark Brown [this message]
2011-07-11 14:16 ` Ashish Chavan
2011-07-11 14:17 ` 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=20110707154933.GB16325@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.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.