From: Lu Guanqun <guanqun.lu@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: tlv320dac33: Lower the OSC calibration time
Date: Mon, 11 Apr 2011 21:05:32 +0800 [thread overview]
Message-ID: <20110411130532.GC11072@qtel.sh.intel.com> (raw)
In-Reply-To: <1302526664-1497-1-git-send-email-peter.ujfalusi@nokia.com>
On Mon, Apr 11, 2011 at 08:57:44PM +0800, Peter Ujfalusi wrote:
> To get correct calibration, we can decrease the time
> needed for the OSC to calibrate itself.
> With this change we can safe ~15ms in the OSC
s/safe/save/
> calibration phase.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
> ---
> sound/soc/codecs/tlv320dac33.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/codecs/tlv320dac33.c b/sound/soc/codecs/tlv320dac33.c
> index c109f6d..401a7ce 100644
> --- a/sound/soc/codecs/tlv320dac33.c
> +++ b/sound/soc/codecs/tlv320dac33.c
> @@ -946,8 +946,8 @@ static int dac33_prepare_chip(struct snd_pcm_substream *substream)
> /* Write registers 0x08 and 0x09 (MSB, LSB) */
> dac33_write16(codec, DAC33_INT_OSC_FREQ_RAT_A, oscset);
>
> - /* calib time: 128 is a nice number ;) */
> - dac33_write(codec, DAC33_CALIB_TIME, 128);
> + /* OSC calibration time */
> + dac33_write(codec, DAC33_CALIB_TIME, 96);
>
> /* adjustment treshold & step */
> dac33_write(codec, DAC33_INT_OSC_CTRL_B, DAC33_ADJTHRSHLD(2) |
> --
> 1.7.4.1
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
guanqun
next prev parent reply other threads:[~2011-04-11 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 12:57 [PATCH] ASoC: tlv320dac33: Lower the OSC calibration time Peter Ujfalusi
2011-04-11 13:05 ` Lu Guanqun [this message]
2011-04-11 14:51 ` peter.ujfalusi
2011-04-11 13:40 ` 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=20110411130532.GC11072@qtel.sh.intel.com \
--to=guanqun.lu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 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.