Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mark Brown <broonie@kernel.org>
Cc: 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,
	mazziesaccount@gmail.com, mcoquelin.stm32@gmail.com,
	 alexandre.torgue@foss.st.com, 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 00/18] mfd: convert to use maple tree register cache
Date: Tue, 6 Feb 2024 11:14:11 +0100	[thread overview]
Message-ID: <CAMuHMdVj1bS9s69ASrd5xULc8oELoBbnb8HEX9MEmA43853_EQ@mail.gmail.com> (raw)
In-Reply-To: <ZcIE/RMTq34TgpQt@finisterre.sirena.org.uk>

Hi Mark,

On Tue, Feb 6, 2024 at 11:09 AM Mark Brown <broonie@kernel.org> wrote:
> On Tue, Feb 06, 2024 at 10:33:22AM +0100, Geert Uytterhoeven wrote:
> > If all of this is true, is there any reason to keep REGCACHE_RBTREE
> > around?  If not, perhaps REGCACHE_RBTREE should be treated as
> > REGCACHE_MAPLE in the regmap core code first, followed by a single
> > tree-wide patch to replace REGCACHE_RBTREE?
>
> There is a very small niche for devices where cache syncs are a
> particularly important part of the workload where rbtree's choices might
> give better performance, especially on systems with low end CPUs.

The REGCACHE_* value is specified by the device, not by the CPU?
While some of these MFD devices are on-SoC, and thus there is some
relation between device and CPU, several others (e.g. PMICs) are
external, and thus might be present on systems with a variety of CPU
performance.

Perhaps the value should depend on some CPU heuristic instead?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2024-02-06 10:14 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
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 [this message]
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=CAMuHMdVj1bS9s69ASrd5xULc8oELoBbnb8HEX9MEmA43853_EQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=broonie@kernel.org \
    --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=mazziesaccount@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