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: Fri, 1 Jul 2011 09:17:50 -0700 [thread overview]
Message-ID: <20110701161749.GD23784@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1309509205.15931.89.camel@matrix>
On Fri, Jul 01, 2011 at 02:03:25PM +0530, Ashish Chavan wrote:
> On Thu, 2011-06-30 at 22:07 +0530, Mark Brown wrote:
> > You'd need to implement custom controls for the relevant enables which
> > check to see what is currently enabled and prevents enables if there
> > are conflicts. You should do this dynamically and I'd expect that only
> > the enables actually need to check anything, adjusting parameters for
> > things that aren't active is usually no problem.
> I see. That means it's ok to allow setting up values of five band
> equalizers even when overall equalizer functionality is disabled.
> Can you point me to any existing code that has such custom control(s)
> which need to check for similar conditions? I am sure that many existing
> codecs would have this kind of inter dependent functions.
This requirement is actually fairly unusual, but there's plenty of
drivers with open coded controls for various reasons. Have you tried
looking at the existing drivers in mainline?
next prev parent reply other threads:[~2011-07-01 16:17 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 [this message]
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
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=20110701161749.GD23784@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.