From: Bo Liu <liubo03@inspur.com>
To: <support.opensource@diasemi.com>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>,
<jagan@amarulasolutions.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, Bo Liu <liubo03@inspur.com>
Subject: [PATCH v1 10/13] regulator: rtq6752: convert to use maple tree register cache
Date: Wed, 20 Mar 2024 04:57:37 -0400 [thread overview]
Message-ID: <20240320085740.4604-11-liubo03@inspur.com> (raw)
In-Reply-To: <20240320085740.4604-1-liubo03@inspur.com>
The maple tree register cache is based on a much more modern data structure
than the rbtree cache and makes optimisation choices which are probably
more appropriate for modern systems than those made by the rbtree cache.
Signed-off-by: Bo Liu <liubo03@inspur.com>
---
drivers/regulator/rtq6752-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/rtq6752-regulator.c b/drivers/regulator/rtq6752-regulator.c
index 8176e5ab0683..d35d844eff3b 100644
--- a/drivers/regulator/rtq6752-regulator.c
+++ b/drivers/regulator/rtq6752-regulator.c
@@ -209,7 +209,7 @@ static const struct reg_default rtq6752_reg_defaults[] = {
static const struct regmap_config rtq6752_regmap_config = {
.reg_bits = 8,
.val_bits = 8,
- .cache_type = REGCACHE_RBTREE,
+ .cache_type = REGCACHE_MAPLE,
.max_register = RTQ6752_REG_FAULT,
.reg_defaults = rtq6752_reg_defaults,
.num_reg_defaults = ARRAY_SIZE(rtq6752_reg_defaults),
--
2.18.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-20 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 8:57 [PATCH v1 00/13] regulator: convert to use maple tree register cache Bo Liu
2024-03-20 8:57 ` [PATCH v1 01/13] regulator: da9121: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 02/13] regulator: da9211: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 03/13] regulator: isl9305: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 04/13] regulator: max8973: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 05/13] regulator: mt6311: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 06/13] regulator: pca9450: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 07/13] regulator: pf8x00: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 08/13] regulator: pfuze100: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 09/13] regulator: rtmv20: " Bo Liu
2024-03-20 8:57 ` Bo Liu [this message]
2024-03-20 8:57 ` [PATCH v1 11/13] regulator: tps51632: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 12/13] regulator: tps62360: " Bo Liu
2024-03-20 8:57 ` [PATCH v1 13/13] regulator: rpi-panel-attiny: " Bo Liu
2024-03-26 12:39 ` [PATCH v1 00/13] regulator: " Mark Brown
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=20240320085740.4604-11-liubo03@inspur.com \
--to=liubo03@inspur.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=support.opensource@diasemi.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