Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Irestål" <andreas.irestal@axis.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "Andreas Irestål" <andire@axis.com>,
	liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org,
	broonie@kernel.org
Subject: Re: [PATCH] ASoC: adau17x1: Cache writes when core clock is disabled
Date: Thu, 4 Feb 2016 20:01:30 +0100	[thread overview]
Message-ID: <20160204190129.GA32441@lnxandire1.se.axis.com> (raw)
In-Reply-To: <56B38938.40000@metafoo.de>

On Thu, Feb 04, 2016 at 06:24:08PM +0100, Lars-Peter Clausen wrote:
> On 02/04/2016 06:22 PM, Lars-Peter Clausen wrote:
> [...]
> >> +	/* Enable cache only mode as we could miss writes before bias level
> >> +	 * reaches standby and the core clock is enabled */
> >> +	regcache_cache_only(regmap, true);
> >> +
> > 
> > There are a few register writes before this where the hardware configuration
> > is setup. When I look at my test setup those writes seem to go through, even
> > though they shouldn't according to what you say (and to what is written in
> > the datasheet).
> > 
> > On the other hand I've never seen the issue you are having either and I've
> > tested both master and slave configuration of the device. Maybe something
> > changed in the silicon in newer revisions of the device. Can you take a look
> > whether the hardware configuration is correctly applied for you?
> 
> Ah, no, ignore that. Those writes happen later on.
> 

The whole thing depends on what driver you are using. We had our own
board drivers before moving to DT, where we would call set_dai_fmt in
hw_params, so the register would get written again before we wanted to
do something useful anyway. The simple-card driver only set the dai format
at probing time and never again, so that's why we started to notice this
issue.

I posted a set of patches a few days ago which added DT support and
fixed minor things in adau17x1, but I realized I was clumsy just sending
it to the alsa-devel list and not including DT maintainers or any
maintainers at all. Would you have a look at it, or do you want me to
resubmit the patches with the correct recipents?

/Andreas

  reply	other threads:[~2016-02-04 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 14:05 [PATCH] ASoC: adau17x1: Cache writes when core clock is disabled Andreas Irestål
2016-02-04 17:22 ` Lars-Peter Clausen
2016-02-04 17:24   ` Lars-Peter Clausen
2016-02-04 19:01     ` Andreas Irestål [this message]
2016-02-04 19:34       ` Mark Brown
2016-02-05 13:35 ` Applied "ASoC: adau17x1: Cache writes when core clock is disabled" to the asoc tree 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=20160204190129.GA32441@lnxandire1.se.axis.com \
    --to=andreas.irestal@axis.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andire@axis.com \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=liam.r.girdwood@linux.intel.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