alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Christian Glindkamp <christian.glindkamp@taskit.de>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Add MAX9850 codec driver
Date: Tue, 8 Mar 2011 12:09:52 +0000	[thread overview]
Message-ID: <20110308120952.GA13671@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110308115254.GD7902@taskit.de>

On Tue, Mar 08, 2011 at 12:52:54PM +0100, Christian Glindkamp wrote:
> Do I understand it correctly, that all register writes that I do in the
> probe function would be overridden by the syncing so they would have to
> be moved to the standby code or put into the register cache array as
> default values?

If you do any registers writes in the probe() function, in effect you
will be changing the hardware state as well as the cache state.  If
after that point you sync the cache to the hardware, the altered cache
will be synced, not the defaults cache.  The core makes a copy of the
defaults cache and uses that for syncing, or if you don't provide a
default's cache it will use a zero-ed cache.

Note that volatile registers don't affect the cache, they bypass it
completely.

Thanks,
Dimitris

  reply	other threads:[~2011-03-08 12:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 12:45 [PATCH] ASoC: Add MAX9850 codec driver Christian Glindkamp
2011-03-07 13:48 ` Dimitris Papastamos
2011-03-07 17:04   ` Christian Glindkamp
2011-03-07 17:14     ` Mark Brown
2011-03-08 10:14     ` Dimitris Papastamos
2011-03-08 11:52       ` Christian Glindkamp
2011-03-08 12:09         ` Dimitris Papastamos [this message]
2011-03-07 15:15 ` Mark Brown
2011-03-08  9:51   ` Christian Glindkamp
2011-03-07 16:40 ` Seungwhan Youn
2011-03-08 10:21   ` Dimitris Papastamos
2011-03-09 10:20 ` [PATCH v2] " Christian Glindkamp
2011-03-09 14:31   ` Dimitris Papastamos
2011-03-11 11:06   ` Liam Girdwood
2011-03-11 12:09   ` 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=20110308120952.GA13671@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=christian.glindkamp@taskit.de \
    --cc=lrg@slimlogic.co.uk \
    /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).