summaryrefslogtreecommitdiffstats
path: root/Documentation/memory.txt
diff options
context:
space:
mode:
authorDimitris Papastamos <dp@opensource.wolfsonmicro.com>2011-09-19 14:34:02 +0100
committerMark Brown <broonie@opensource.wolfsonmicro.com>2011-09-19 19:06:33 +0100
commit28644c809f44498b8cd91d00b4cdb09e63b99843 (patch)
tree6a21cc679053956e00106cc31356a699ef70fca0 /Documentation/memory.txt
parent195af65ca92179ac2b524d35d732dc6fecec2744 (diff)
downloadblackbird-op-linux-28644c809f44498b8cd91d00b4cdb09e63b99843.tar.gz
blackbird-op-linux-28644c809f44498b8cd91d00b4cdb09e63b99843.zip
regmap: Add the rbtree cache support
This patch adds support for the rbtree cache compression type. Each rbnode manages a variable length block of registers. There can be no two nodes with overlapping blocks. Each block has a base register and a currently top register, all the other registers, if any, lie in between these two and in ascending order. The reasoning behind the construction of this rbtree is simple. In the snd_soc_rbtree_cache_init() function, we iterate over the register defaults provided by the regcache core. For each register value that is non-zero we insert it in the rbtree. In order to determine in which rbnode we need to add the register, we first look if there is another register already added that is adjacent to the one we are about to add. If that is the case we append it in that rbnode block, otherwise we create a new rbnode with a single register in its block and add it to the tree. There are various optimizations across the implementation to speed up lookups by caching the most recently used rbnode. Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com> Tested-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Diffstat (limited to 'Documentation/memory.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud