From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Zhang Quan-B13634 <B13634@freescale.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [PATCH 3/4] ASOC: imx: add machine driver using wm8962 codec
Date: Thu, 31 Jan 2013 11:23:36 +0800 [thread overview]
Message-ID: <20130131032334.GB6027@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <8D894AC610DA3944965280D4097EAC4603CCB754@039-SN2MPN1-021.039d.mgd.msft.net>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
On Thu, Jan 31, 2013 at 03:02:21AM +0000, Zhang Quan-B13634 wrote:
> > > + if (!codec_dai->active)
> > > + clk_enable(data->codec_clk);
> > Should be clk_prepare_enable() but it's not clear to me why you need
> > this... Also the clock API does refcounting so there should be no need
> > to check for active, you should get matching startups and shutdowns.
> >
> > This will also fail for analogue bypass paths, set_bias_level() would be a good
> > place to cover those.
> [Gary-b13634] for power saving consideration. For now remove this feature to
> Implement a basic feature
I get why you're doing this at all but doing it in startup seems odd -
like I say set_bias_level() is the most idiomatic place to implement
this usually. There's a few machine drivers doing that you should be
able to refer to for examples.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2013-01-31 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1359445790-2070-1-git-send-email-b13634@freescale.com>
2013-01-29 9:07 ` [PATCH 3/4] ASOC: imx: add machine driver using wm8962 codec Mark Brown
[not found] ` <8D894AC610DA3944965280D4097EAC4603CCB754@039-SN2MPN1-021.039d.mgd.msft.net>
2013-01-31 3:23 ` Mark Brown [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=20130131032334.GB6027@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B13634@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=shawn.guo@linaro.org \
/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.