From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Input: cap11xx - Convert to use maple tree register cache
Date: Mon, 2 Oct 2023 23:16:51 -0700 [thread overview]
Message-ID: <ZRux0yLPxZGLNF5A@google.com> (raw)
In-Reply-To: <20231001-input-maple-v1-2-ed3716051431@kernel.org>
Hi Mark,
On Sun, Oct 01, 2023 at 01:43:39AM +0200, Mark Brown 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.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> drivers/input/keyboard/cap11xx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/cap11xx.c b/drivers/input/keyboard/cap11xx.c
> index 39ed3b9ddc65..77843ad15d4c 100644
> --- a/drivers/input/keyboard/cap11xx.c
> +++ b/drivers/input/keyboard/cap11xx.c
> @@ -174,7 +174,7 @@ static const struct regmap_config cap11xx_regmap_config = {
> .reg_defaults = cap11xx_reg_defaults,
>
> .num_reg_defaults = ARRAY_SIZE(cap11xx_reg_defaults),
> - .cache_type = REGCACHE_RBTREE,
> + .cache_type = REGCACHE_MAPLE,
I do not think these driver care much about the cache type. Optimal one
might even depend on the architecture. I wonder if we could have
something like REGCACHE_DEFAULT to signal that whatever is the "best
default" implementation it should be used?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2023-10-03 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 23:43 [PATCH 0/3] Input: Small regmap improvements Mark Brown
2023-09-30 23:43 ` [PATCH 1/3] Input: cap11xx - Cache hardware ID registers Mark Brown
2023-09-30 23:43 ` [PATCH 2/3] Input: cap11xx - Convert to use maple tree register cache Mark Brown
2023-10-03 6:16 ` Dmitry Torokhov [this message]
2023-10-03 12:16 ` Mark Brown
2023-09-30 23:43 ` [PATCH 3/3] Input: qt1050 " Mark Brown
2023-12-13 5:39 ` [PATCH 0/3] Input: Small regmap improvements Dmitry Torokhov
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=ZRux0yLPxZGLNF5A@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox