From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>, pascal.huerst@gmail.com
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: adau1701: Reset codec based on sample rate changes
Date: Wed, 23 Mar 2016 14:37:10 +0100 [thread overview]
Message-ID: <56F29C06.3090004@metafoo.de> (raw)
In-Reply-To: <20160323124849.GL2566@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 929 bytes --]
On 03/23/2016 01:48 PM, Mark Brown wrote:
> On Wed, Mar 23, 2016 at 12:58:23PM +0100, pascal.huerst@gmail.com wrote:
>
>> Instead of checking if mclk/lrclk ratio has changed, check if
>> sample rate has changed. In certain cases, the mclk might be
>> changed in the machine driver, which can lead to the same
>> mclk/lrclk ration, eventhow the sample rate has changed.
>
>> Since the codec has to be programmed differently for every
>> sample rate, its better to check for samplerate changes instead
>> of mclk/lrclk ration changes.
>
> Why does this mean we have to reset the CODEC rather than just
> reprogramming it?
Quoting from the datasheet:
The clock mode should not be changed without also resetting
the ADAU1701. If the mode is changed during operation, a
click or pop can result in the output signals. The state of the
PLL_MODEx pins should be changed while RESET is held low.
- Lars
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-03-23 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:58 [PATCH] ASoC: adau1701: Reset codec based on sample rate changes pascal.huerst
2016-03-23 12:48 ` Mark Brown
2016-03-23 13:37 ` Lars-Peter Clausen [this message]
2016-03-23 13:42 ` Mark Brown
2016-03-23 13:44 ` Lars-Peter Clausen
2016-03-24 16:48 ` Pascal Huerst
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=56F29C06.3090004@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pascal.huerst@gmail.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).