From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>, lrg <lrg@ti.com>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH v2] ASoC: codecs: Add DA9055 codec driver
Date: Tue, 18 Sep 2012 22:50:36 -0400 [thread overview]
Message-ID: <20120919025035.GI8832@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1347622057.16763.27.camel@matrix>
On Fri, Sep 14, 2012 at 04:57:37PM +0530, Ashish Chavan wrote:
This looks like a good improvement, a few issues remain though:
> + /* DAC Routing control */
> + SOC_ENUM("DAC Left Select", da9055_dac_l_select),
> + SOC_ENUM("DAC Right Select", da9055_dac_r_select),
DAPM. This even says its a routing control...
> + /* To select if MIC Bias powers MIC 1 or MIC 2 */
> + SOC_ENUM("Mic Bias Select", da9055_mic_bias_select),
This would normally be something controlled by the board... what
exactly is this doing? How does the MICBIAS relate to the microphone
inputs?
> + case SND_SOC_BIAS_STANDBY:
> + if (codec->dapm.bias_level == SND_SOC_BIAS_OFF) {
> + /* Enable VMID reference & master bias */
> + snd_soc_update_bits(codec, DA9055_REFERENCES,
> + DA9055_VMID_EN | DA9055_BIAS_EN,
> + DA9055_VMID_EN | DA9055_BIAS_EN);
> + }
> + regcache_sync(da9055->regmap);
Doing the sync every time is very odd, why is it only done on
transitions from _OFF? Given that there's no regulator support here
it's also a bit surprising that you need to do a sync outside of system
suspend...
> + da9055->mclk_rate = 0; /* This will be set from set_sysclk() */
> + da9055->master = 0; /* This will be set from set_fmt() */
You use kzalloc...
next prev parent reply other threads:[~2012-09-19 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 11:27 [PATCH v2] ASoC: codecs: Add DA9055 codec driver Ashish Chavan
2012-09-19 2:50 ` Mark Brown [this message]
2012-09-20 11:58 ` Ashish Chavan
2012-09-20 11:59 ` 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=20120919025035.GI8832@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.com \
--cc=david.chen@diasemi.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).