From: Mark Brown <broonie@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Alex Helms <alexander.helms.jy@renesas.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH 2/4] clk: versaclock3: Convert to use maple tree register cache
Date: Fri, 29 Sep 2023 16:26:06 +0200 [thread overview]
Message-ID: <20230929-clk-maple-versaclk-v1-2-24dd5b3d8689@kernel.org> (raw)
In-Reply-To: <20230929-clk-maple-versaclk-v1-0-24dd5b3d8689@kernel.org>
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: Mark Brown <broonie@kernel.org>
---
drivers/clk/clk-versaclock3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-versaclock3.c b/drivers/clk/clk-versaclock3.c
index a5ab48ff242c..b4a89c083c11 100644
--- a/drivers/clk/clk-versaclock3.c
+++ b/drivers/clk/clk-versaclock3.c
@@ -589,7 +589,7 @@ static const struct clk_ops vc3_clk_mux_ops = {
static const struct regmap_config vc3_regmap_config = {
.reg_bits = 8,
.val_bits = 8,
- .cache_type = REGCACHE_RBTREE,
+ .cache_type = REGCACHE_MAPLE,
.max_register = 0x24,
};
--
2.39.2
next prev parent reply other threads:[~2023-09-29 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 14:26 [PATCH 0/4] clk: versaclock: regmap modernisations Mark Brown
2023-09-29 14:26 ` [PATCH 1/4] clk: versaclock3: Remove redundant _is_writeable() Mark Brown
2023-10-10 3:32 ` Stephen Boyd
2023-09-29 14:26 ` Mark Brown [this message]
2023-10-10 3:32 ` [PATCH 2/4] clk: versaclock3: Convert to use maple tree register cache Stephen Boyd
2023-09-29 14:26 ` [PATCH 3/4] clk: versaclock5: " Mark Brown
2023-10-10 3:32 ` Stephen Boyd
2023-09-29 14:26 ` [PATCH 4/4] clk: versaclock7: " Mark Brown
2023-10-10 3:31 ` Stephen Boyd
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=20230929-clk-maple-versaclk-v1-2-24dd5b3d8689@kernel.org \
--to=broonie@kernel.org \
--cc=alexander.helms.jy@renesas.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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
all inboxes | Powered by JetHome®