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 v2 0/3] ASoC: Introduce the new caching API
Date: Thu, 11 Nov 2010 16:23:50 +0000 [thread overview]
Message-ID: <1289492631.24548.0.camel@dplaptop> (raw)
In-Reply-To: <20101111162002.GG6052@rakim.wolfsonmicro.main>
On Thu, 2010-11-11 at 16:20 +0000, Mark Brown wrote:
> On Thu, Nov 11, 2010 at 10:04:56AM +0000, Dimitris Papastamos wrote:
> > This patch series introduces the new caching API. The idea behind this
> > caching interface is that we can provide different means of organizing
> > and accessing the register cache. This is useful for large and sparse
> > register maps, where one can use some kind of compression algorithm to
> > reduce the memory footprint. The caching API is designed in such way to
> > eliminate the need for modifying any existing drivers.
>
> Applied, thanks.
>
> > TODO:
> > - Memory usage statistics, to make it easier to select the proper caching
> > technique.
> > - Support for bulk reads/writes.
> > - Overridable caching behaviour from the machine driver.
>
> This one in particular would be very good.
Yes, I have an idea on how to do that. I will send you a patch at some
point.
Thanks,
Dimitrios
prev parent reply other threads:[~2010-11-11 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 10:04 [PATCH v2 0/3] ASoC: Introduce the new caching API Dimitris Papastamos
2010-11-11 10:04 ` [PATCH 1/3] ASoC: soc-cache: Add support for flat register caching Dimitris Papastamos
2010-11-11 10:04 ` [PATCH 2/3] ASoC: soc-cache: Add support for LZO " Dimitris Papastamos
2010-11-11 10:04 ` [PATCH 3/3] ASoC: soc-cache: Add support for rbtree based " Dimitris Papastamos
2010-11-11 11:39 ` [PATCH v2 0/3] ASoC: Introduce the new caching API Liam Girdwood
2010-11-11 16:20 ` Mark Brown
2010-11-11 16:23 ` Dimitris Papastamos [this message]
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=1289492631.24548.0.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).