alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2/4] ASoC: soc-cache: Add support for flat register caching
Date: Fri, 5 Nov 2010 09:31:44 -0400	[thread overview]
Message-ID: <20101105133143.GH13709@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1288949677.8256.14.camel@dplaptop>

On Fri, Nov 05, 2010 at 09:34:37AM +0000, Dimitris Papastamos wrote:
> On Thu, 2010-11-04 at 14:31 -0400, Mark Brown wrote:

> > > +	mutex_init(&cache_rw_mutex);
> > > +

> > I'd kind of expect this to be with the other cache setup?

> Do you mean that the mutex should also be used with the other caching
> techniques?  That is not needed because we currently lock at a higher
> level, in the function that delegates the calls to the implementation
> functions.

I'd expect this to be with the rest of the initialisation for the
structure that it's embedded in - having this be initialised in this
place separately to anything else feels wrong.  Of course at the minute
it's not in a structure (which I raised as an issue as well IIRC) which
means that we'll have an issue with multiple initialisation if two
devices are registered.

> > Are you sure that all the CODECs that rely on the existing shared
> > register cache are going to call this?

> What do you mean by 'shared register cache'?  Each codec gets its own
> copy of their register cache.

The shared register cache support code.

> Any CODEC driver that calls snd_soc_register_codec() and has provided
> reg_cache_size and reg_word_size will have soc-core setting up its cache
> accordingly.  By default the provided snd_soc_codec_driver is zero-ed
> out, so its compress_type will default to the flat compression type.

Are you absolutely positive that every user of the code is using a
register cache initialised using that method?

  reply	other threads:[~2010-11-05 13:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:22 [PATCH 0/4] ASoC: Introduce the new caching API Dimitris Papastamos
2010-11-04 14:22 ` [PATCH 1/4] ASoC: soc.h: Add new caching API prototypes and hooks Dimitris Papastamos
2010-11-04 18:20   ` Mark Brown
2010-11-04 14:22 ` [PATCH 2/4] ASoC: soc-cache: Add support for flat register caching Dimitris Papastamos
2010-11-04 18:31   ` Mark Brown
2010-11-05  9:34     ` Dimitris Papastamos
2010-11-05 13:31       ` Mark Brown [this message]
2010-11-05 13:59         ` Dimitris Papastamos
2010-11-05 14:07           ` Mark Brown
2010-11-05 14:12             ` Dimitris Papastamos
2010-11-05 15:25               ` Mark Brown
2010-11-05 11:45     ` Dimitris Papastamos
2010-11-04 14:22 ` [PATCH 3/4] ASoC: soc-cache: Add support for LZO " Dimitris Papastamos
2010-11-04 22:45   ` Mark Brown
2010-11-05 10:22     ` Dimitris Papastamos
2010-11-05 13:33       ` Mark Brown
2010-11-04 14:22 ` [PATCH 4/4] ASoC: soc-cache: Add support for rbtree based " Dimitris Papastamos
2010-11-04 18:49   ` Mark Brown
2010-11-04 18:50     ` Mark Brown
2010-11-05  9:38     ` Dimitris Papastamos

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=20101105133143.GH13709@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=patches@opensource.wolfsonmicro.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).