summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2023-04-25 19:03:33 +0100
committerLee Jones <lee@kernel.org>2023-06-15 09:19:36 +0100
commit7ef47a12a62e8fcf1b66a401cd6f3fc055581da0 (patch)
tree1e3c404c71d0f260fabedcb2cbebf6e187dcbab5
parent867cae44f8ae150d0e303cfd62a01d0d7cd7f7a5 (diff)
downloadlinux-stable-7ef47a12a62e8fcf1b66a401cd6f3fc055581da0.tar.gz
linux-stable-7ef47a12a62e8fcf1b66a401cd6f3fc055581da0.tar.bz2
linux-stable-7ef47a12a62e8fcf1b66a401cd6f3fc055581da0.zip
mfd: wm831x: Use maple tree register cache
regmap has introduced a maple tree based register cache which makes use of this more advanced data structure which has been added to the kernel recently. Maple trees are much flatter than rbtrees, meaning that they do not grow to such depths when the register map is sparse which makes access a bit more efficient. The maple tree cache type is still a bit of a work in progress but should be effective for some devices already. The wm831x devices have a pretty sparse register map and being always on devices never do cache syncs so don't hit the major current disadvantage so they should be good candiates for using the maple tree cache. Update to do so, there should be little if any visible difference at runtime. Signed-off-by: Mark Brown <broonie@kernel.org> Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com> Signed-off-by: Lee Jones <lee@kernel.org> Link: https://lore.kernel.org/r/20230419-mfd-wm831x-maple-v1-1-e03e39d7bb0b@kernel.org
-rw-r--r--drivers/mfd/wm831x-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mfd/wm831x-core.c b/drivers/mfd/wm831x-core.c
index d2f444d2ae78..e86b6a4896a6 100644
--- a/drivers/mfd/wm831x-core.c
+++ b/drivers/mfd/wm831x-core.c
@@ -1430,7 +1430,7 @@ struct regmap_config wm831x_regmap_config = {
.reg_bits = 16,
.val_bits = 16,
- .cache_type = REGCACHE_RBTREE,
+ .cache_type = REGCACHE_MAPLE,
.max_register = WM831X_DBE_CHECK_DATA,
.readable_reg = wm831x_reg_readable,