alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: ADAU1761 default register value problem
Date: Fri, 13 May 2016 10:20:33 +0200	[thread overview]
Message-ID: <57358E51.7020000@metafoo.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1605111440510.31333@lnxricardw1.se.axis.com>

On 05/11/2016 05:16 PM, Ricard Wanderlof wrote:
> 
> Hi Lars,
> 
> On Tue, 26 Apr 2016, Lars-Peter Clausen wrote:
> 
>>> A while ago I posted a question to the list regarding the default values 
>>> set up for the ADAU1761 (and similar CODECs), 
>>> ...
> 
> Having researched this further, it appears that commit
> 
> 27d6e7d1c96c9f51379e0feb972fec26029098bc
> 
> ASoC: adau17x1: Cache writes when core clock is disabled

I think it is also related to commit 1c79771a7270 ("regmap: Use
regcache_mark_dirty() to indicate power loss or reset"). This changes the
regmap code to sync all registers under certain conditions.

> 
> actually fixes this problem, at least for the ADAU1361 and ADAU1761. I'm 
> no expert at the regcache mechanism, but it looks as if when the regcache 
> is synced when the bias level goes from OFF to STANDBY, it actually writes 
> out all the values including the default ones (verified by adding trace 
> printouts, and also by verifying that my original problem of the codec 
> misbehaving after reconfiguration after reboot is no longer there).


We still have the issue though that the CODEC is in an undefined state until
the first OFF to STANDBY transitions happens. Usually this will happen early
on when the CODEC is bound to the sound card, but if it is not bound
immediately it might stay there for a bit longer. So depending on the setup
this may or may not be a problem.

  reply	other threads:[~2016-05-13  8:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 14:01 ADAU1761 default register value problem Ricard Wanderlof
2016-04-26  8:21 ` Lars-Peter Clausen
2016-05-03  8:16   ` Ricard Wanderlof
2016-05-11 15:16   ` Ricard Wanderlof
2016-05-13  8:20     ` Lars-Peter Clausen [this message]
2016-05-16 11:07       ` Ricard Wanderlof
2016-05-16 17:02         ` Lars-Peter Clausen
  -- strict thread matches above, loose matches on Subject: below --
2016-03-29 13:58 Ricard Wanderlof

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=57358E51.7020000@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ricard.wanderlof@axis.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).