All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Bo Liu <liubo03@inspur.com>
To: <dan@dlrobertson.com>, <jic23@kernel.org>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Bo Liu <liubo03@inspur.com>
Subject: [PATCH 2/4] iio: accel: bma400: convert to use maple tree register cache
Date: Wed, 12 Feb 2025 02:52:21 -0500	[thread overview]
Message-ID: <20250212075223.4164-3-liubo03@inspur.com> (raw)
In-Reply-To: <20250212075223.4164-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/iio/accel/bma400_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/accel/bma400_core.c b/drivers/iio/accel/bma400_core.c
index ae806ed60271..23f5e1ce9cc4 100644
--- a/drivers/iio/accel/bma400_core.c
+++ b/drivers/iio/accel/bma400_core.c
@@ -190,7 +190,7 @@ const struct regmap_config bma400_regmap_config = {
 	.reg_bits = 8,
 	.val_bits = 8,
 	.max_register = BMA400_CMD_REG,
-	.cache_type = REGCACHE_RBTREE,
+	.cache_type = REGCACHE_MAPLE,
 	.writeable_reg = bma400_is_writable_reg,
 	.volatile_reg = bma400_is_volatile_reg,
 };
-- 
2.31.1


  parent reply	other threads:[~2025-02-12  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  7:52 [PATCH 0/4] iio: accel: convert to use maple tree register cache Bo Liu
2025-02-12  7:52 ` [PATCH 1/4] iio: accel: msa311: " Bo Liu
2025-02-12  7:52 ` Bo Liu [this message]
2025-02-12  7:52 ` [PATCH 3/4] iio: accel: bmi088: " Bo Liu
2025-02-12  7:52 ` [PATCH 4/4] iio: accel: kx022a: " Bo Liu
2025-02-14  6:36   ` Matti Vaittinen
2025-02-16 16:38 ` [PATCH 0/4] iio: accel: " Jonathan Cameron

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=20250212075223.4164-3-liubo03@inspur.com \
    --to=liubo03@inspur.com \
    --cc=dan@dlrobertson.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.