From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: tlv320dac33: Move codec power up to DAPM
Date: Thu, 24 Mar 2011 10:15:58 +0000 [thread overview]
Message-ID: <20110324101557.GC28306@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1300950709-13695-1-git-send-email-peter.ujfalusi@nokia.com>
On Thu, Mar 24, 2011 at 09:11:49AM +0200, Peter Ujfalusi wrote:
> Move the codec power on (in reg 0x01, bit 4) from
> set_bias_level:SND_SOC_BIAS_ON to a DAPM supply.
> In this way we can be sure, that all the things within
> the codec is powered before the external amp is
> going to be enabled.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2011-03-24 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 7:11 [PATCH] ASoC: tlv320dac33: Move codec power up to DAPM Peter Ujfalusi
2011-03-24 10:15 ` Mark Brown [this message]
2011-03-26 15:52 ` Liam Girdwood
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=20110324101557.GC28306@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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).