From: Mark Brown <broonie@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 1/4] leds: lm3601x: Convert to use maple tree register cache
Date: Fri, 29 Sep 2023 17:23:35 +0200 [thread overview]
Message-ID: <20230929-leds-maple-v1-1-ba5f9dcb1e75@kernel.org> (raw)
In-Reply-To: <20230929-leds-maple-v1-0-ba5f9dcb1e75@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/leds/flash/leds-lm3601x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/leds/flash/leds-lm3601x.c b/drivers/leds/flash/leds-lm3601x.c
index b6c524facf49..8191be0ef0c6 100644
--- a/drivers/leds/flash/leds-lm3601x.c
+++ b/drivers/leds/flash/leds-lm3601x.c
@@ -123,7 +123,7 @@ static const struct regmap_config lm3601x_regmap = {
.max_register = LM3601X_DEV_ID_REG,
.reg_defaults = lm3601x_regmap_defs,
.num_reg_defaults = ARRAY_SIZE(lm3601x_regmap_defs),
- .cache_type = REGCACHE_RBTREE,
+ .cache_type = REGCACHE_MAPLE,
.volatile_reg = lm3601x_volatile_reg,
};
--
2.39.2
next prev parent reply other threads:[~2023-09-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:23 [PATCH 0/4] leds: Convert to use maple tree register cache Mark Brown
2023-09-29 15:23 ` Mark Brown [this message]
2023-09-29 15:23 ` [PATCH 2/4] leds: aw200xx: " Mark Brown
2023-09-29 15:23 ` [PATCH 3/4] leds: lm392x: " Mark Brown
2023-09-29 15:23 ` [PATCH 4/4] leds: lp3952: " Mark Brown
2023-10-05 11:10 ` [PATCH 0/4] leds: " Lee Jones
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-leds-maple-v1-1-ba5f9dcb1e75@kernel.org \
--to=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).