From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Bo Liu <liubo03@inspur.com>,
lee@kernel.org, wens@csie.org, marek.vasut+renesas@gmail.com,
support.opensource@diasemi.com, neil.armstrong@linaro.org,
ckeepax@opensource.cirrus.com, rf@opensource.cirrus.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-amlogic@lists.infradead.org, patches@opensource.cirrus.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 11/18] mfd: rohm: convert to use maple tree register cache
Date: Wed, 7 Feb 2024 09:57:54 +0200 [thread overview]
Message-ID: <ab8d9d0a-aad4-42b7-9e24-9ae6acf7c939@gmail.com> (raw)
In-Reply-To: <20240206071314.8721-12-liubo03@inspur.com>
On 2/6/24 09:13, Bo Liu 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: Bo Liu <liubo03@inspur.com>
Acked-by: Matti Vaittinen <mazziesaccount@gmail.com>
> ---
> drivers/mfd/rohm-bd71828.c | 4 ++--
> drivers/mfd/rohm-bd718x7.c | 2 +-
> drivers/mfd/rohm-bd9576.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mfd/rohm-bd71828.c b/drivers/mfd/rohm-bd71828.c
> index 594718f7e8e1..2f3826c7eef4 100644
> --- a/drivers/mfd/rohm-bd71828.c
> +++ b/drivers/mfd/rohm-bd71828.c
> @@ -197,7 +197,7 @@ static const struct regmap_config bd71815_regmap = {
> .val_bits = 8,
> .volatile_table = &bd71815_volatile_regs,
> .max_register = BD71815_MAX_REGISTER - 1,
> - .cache_type = REGCACHE_RBTREE,
> + .cache_type = REGCACHE_MAPLE,
> };
>
> static const struct regmap_config bd71828_regmap = {
> @@ -205,7 +205,7 @@ static const struct regmap_config bd71828_regmap = {
> .val_bits = 8,
> .volatile_table = &bd71828_volatile_regs,
> .max_register = BD71828_MAX_REGISTER,
> - .cache_type = REGCACHE_RBTREE,
> + .cache_type = REGCACHE_MAPLE,
> };
>
> /*
> diff --git a/drivers/mfd/rohm-bd718x7.c b/drivers/mfd/rohm-bd718x7.c
> index 4798bdf27afb..7755a4c073bf 100644
> --- a/drivers/mfd/rohm-bd718x7.c
> +++ b/drivers/mfd/rohm-bd718x7.c
> @@ -87,7 +87,7 @@ static const struct regmap_config bd718xx_regmap_config = {
> .val_bits = 8,
> .volatile_table = &volatile_regs,
> .max_register = BD718XX_MAX_REGISTER - 1,
> - .cache_type = REGCACHE_RBTREE,
> + .cache_type = REGCACHE_MAPLE,
> };
>
> static int bd718xx_init_press_duration(struct regmap *regmap,
> diff --git a/drivers/mfd/rohm-bd9576.c b/drivers/mfd/rohm-bd9576.c
> index bceac7016740..3a9f61961721 100644
> --- a/drivers/mfd/rohm-bd9576.c
> +++ b/drivers/mfd/rohm-bd9576.c
> @@ -62,7 +62,7 @@ static struct regmap_config bd957x_regmap = {
> .val_bits = 8,
> .volatile_table = &volatile_regs,
> .max_register = BD957X_MAX_REGISTER,
> - .cache_type = REGCACHE_RBTREE,
> + .cache_type = REGCACHE_MAPLE,
> };
>
> static struct regmap_irq bd9576_irqs[] = {
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-02-07 7:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 7:12 [PATCH 00/18] mfd: convert to use maple tree register cache Bo Liu
2024-02-06 7:12 ` [PATCH 01/18] mfd: ac100: " Bo Liu
2024-02-06 7:12 ` [PATCH 02/18] mfd: as3711: " Bo Liu
2024-02-06 7:12 ` [PATCH 03/18] mfd: as3722: " Bo Liu
2024-02-06 7:13 ` [PATCH 04/18] mfd: axp20x: " Bo Liu
2024-02-06 7:13 ` [PATCH 05/18] mfd: bcm590xx: " Bo Liu
2024-02-06 7:13 ` [PATCH 06/18] mfd: bd9571mwv: " Bo Liu
2024-02-06 7:13 ` [PATCH 07/18] mfd: dialog: " Bo Liu
2024-02-06 7:13 ` [PATCH 08/18] mfd: khadas-mcu: " Bo Liu
2024-02-06 8:47 ` neil.armstrong
2024-02-06 7:13 ` [PATCH 09/18] mfd: lochnagar-i2c: " Bo Liu
2024-02-06 9:58 ` Charles Keepax
2024-02-06 7:13 ` [PATCH 10/18] mfd: wolfson: " Bo Liu
2024-02-06 10:04 ` Charles Keepax
2024-02-06 10:23 ` Charles Keepax
2024-02-06 7:13 ` [PATCH 11/18] mfd: rohm: " Bo Liu
2024-02-07 7:57 ` Matti Vaittinen [this message]
2024-02-06 7:13 ` [PATCH 12/18] mfd: rk8xx: " Bo Liu
2024-02-06 7:13 ` [PATCH 13/18] mfd: rn5t618: " Bo Liu
2024-02-06 7:13 ` [PATCH 14/18] mfd: rsmu_i2c: " Bo Liu
2024-02-06 7:13 ` [PATCH 15/18] mfd: si476x: " Bo Liu
2024-02-06 7:13 ` [PATCH 16/18] mfd: stmfx: " Bo Liu
2024-02-06 7:13 ` [PATCH 17/18] mfd: stpmic1: " Bo Liu
2024-02-06 7:13 ` [PATCH 18/18] mfd: rc5t583: " Bo Liu
2024-02-06 9:33 ` [PATCH 00/18] mfd: " Geert Uytterhoeven
2024-02-06 10:07 ` Mark Brown
2024-02-06 10:14 ` Geert Uytterhoeven
2024-02-06 10:59 ` Mark Brown
2024-02-08 14:24 ` Lee Jones
2024-02-08 14:26 ` 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=ab8d9d0a-aad4-42b7-9e24-9ae6acf7c939@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=lee@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=liubo03@inspur.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=support.opensource@diasemi.com \
--cc=wens@csie.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