From: Jonathan Cameron <jic23@kernel.org>
To: Bo Liu <liubo03@inspur.com>
Cc: <dan@dlrobertson.com>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] iio: accel: convert to use maple tree register cache
Date: Sun, 16 Feb 2025 16:38:39 +0000 [thread overview]
Message-ID: <20250216163839.2055d5e1@jic23-huawei> (raw)
In-Reply-To: <20250212075223.4164-1-liubo03@inspur.com>
On Wed, 12 Feb 2025 02:52:19 -0500
Bo Liu <liubo03@inspur.com> wrote:
> 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.
>
> Bo Liu (4):
> iio: accel: msa311: convert to use maple tree register cache
> iio: accel: bma400: convert to use maple tree register cache
> iio: accel: bmi088: convert to use maple tree register cache
> iio: accel: kx022a: convert to use maple tree register cache
>
> drivers/iio/accel/bma400_core.c | 2 +-
> drivers/iio/accel/bmi088-accel-core.c | 2 +-
> drivers/iio/accel/kionix-kx022a.c | 4 ++--
> drivers/iio/accel/msa311.c | 2 +-
> 4 files changed, 5 insertions(+), 5 deletions(-)
>
These are all fairly small register maps so I doubt it makes much
real difference. Still there is the possibility these get copied
into a driver with a much larger regmap, so fair enough to tidy these
up. Applied to the togreg branch of iio.git and pushed out as testing
for 0-day to take a first look.
Thanks,
Jonathan
prev parent reply other threads:[~2025-02-16 16:38 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 ` [PATCH 2/4] iio: accel: bma400: " Bo Liu
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 ` Jonathan Cameron [this message]
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=20250216163839.2055d5e1@jic23-huawei \
--to=jic23@kernel.org \
--cc=dan@dlrobertson.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.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 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.