alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@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, 05 Nov 2010 09:34:37 +0000	[thread overview]
Message-ID: <1288949677.8256.14.camel@dplaptop> (raw)
In-Reply-To: <20101104183140.GD6088@opensource.wolfsonmicro.com>

On Thu, 2010-11-04 at 14:31 -0400, Mark Brown wrote:

> > @@ -680,6 +722,8 @@ int snd_soc_codec_set_cache_io(struct snd_soc_codec *codec,
> >  		return -EINVAL;
> >  	}
> >  
> > +	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.

> > @@ -3261,6 +3244,16 @@ int snd_soc_register_codec(struct device *dev,
> >  	INIT_LIST_HEAD(&codec->dapm_widgets);
> >  	INIT_LIST_HEAD(&codec->dapm_paths);
> >  
> > +	/* allocate CODEC register cache */
> > +	if (codec_drv->reg_cache_size && codec_drv->reg_word_size) {
> > +		ret = snd_soc_cache_init(codec);
> > +		if (ret < 0) {
> > +			dev_err(codec->dev, "Failed to set cache compression type: %d\n",
> > +				ret);
> > +			goto error_cache;
> > +		}
> > +	}
> 
> 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.

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.

Thanks,
Dimitrios

  reply	other threads:[~2010-11-05  9:34 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 [this message]
2010-11-05 13:31       ` Mark Brown
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=1288949677.8256.14.camel@dplaptop \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@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).