mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>, Peter Rosin <peda@axentia.se>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Mark Brown <broonie@kernel.org>
Subject: [PATCH 02/17] ASoC: max98095: Use maple tree register cache
Date: Mon, 11 Nov 2024 18:47:34 +0000	[thread overview]
Message-ID: <20241111-asoc-maxim-maple-v1-2-baa315dc546b@kernel.org> (raw)
In-Reply-To: <20241111-asoc-maxim-maple-v1-0-baa315dc546b@kernel.org>

The maple tree register cache uses a more modern data structure than the
rbtree cache and makes optimisation choices that are more appropriate for
current hardware, unless there is a specific reason to do something else
then maple is a better choice for most devices. Switch to it.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
 sound/soc/codecs/max98090.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/max98090.c b/sound/soc/codecs/max98090.c
index 2adf744c652634a1539f7c20ca9102e5e8768b01..0454cea0fb13272434a7ed7d023bf519c8a00607 100644
--- a/sound/soc/codecs/max98090.c
+++ b/sound/soc/codecs/max98090.c
@@ -2530,7 +2530,7 @@ static const struct regmap_config max98090_regmap = {
 	.num_reg_defaults = ARRAY_SIZE(max98090_reg),
 	.volatile_reg = max98090_volatile_register,
 	.readable_reg = max98090_readable_register,
-	.cache_type = REGCACHE_RBTREE,
+	.cache_type = REGCACHE_MAPLE,
 };
 
 static const struct i2c_device_id max98090_i2c_id[] = {

-- 
2.39.5


  parent reply	other threads:[~2024-11-11 18:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 18:47 [PATCH 00/17] ASoC: maxim: Convert to use maple tree caches Mark Brown
2024-11-11 18:47 ` [PATCH 01/17] ASoC: max98088: Use maple tree register cache Mark Brown
2024-11-11 18:47 ` Mark Brown [this message]
2024-11-11 18:47 ` [PATCH 03/17] ASoC: max98095: " Mark Brown
2024-11-11 18:47 ` [PATCH 04/17] ASoC: max98363: " Mark Brown
2024-11-11 18:47 ` [PATCH 05/17] ASoC: max98371: " Mark Brown
2024-11-11 18:47 ` [PATCH 06/17] ASoC: max98373: " Mark Brown
2024-11-11 18:47 ` [PATCH 07/17] ASoC: max98388: " Mark Brown
2024-11-11 18:47 ` [PATCH 08/17] ASoC: max98390: " Mark Brown
2024-11-11 18:47 ` [PATCH 09/17] ASoC: max98396: " Mark Brown
2024-11-11 18:47 ` [PATCH 10/17] ASoC: max98504: " Mark Brown
2024-11-11 18:47 ` [PATCH 11/17] ASoC: max98520: " Mark Brown
2024-11-11 18:47 ` [PATCH 12/17] ASoC: max9860: " Mark Brown
2024-11-11 18:47 ` [PATCH 13/17] ASoC: max9867: " Mark Brown
2024-11-11 18:47 ` [PATCH 14/17] ASoC: max9877: " Mark Brown
2024-11-11 18:47 ` [PATCH 15/17] ASoC: max98925: " Mark Brown
2024-11-11 18:47 ` [PATCH 16/17] ASoC: max98926: " Mark Brown
2024-11-11 18:47 ` [PATCH 17/17] ASoC: max98927: " Mark Brown

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=20241111-asoc-maxim-maple-v1-2-baa315dc546b@kernel.org \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=peda@axentia.se \
    /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

all inboxes | Powered by JetHome®