From: Mark Brown <broonie@kernel.org>
To: Jean Delvare <jdelvare@suse.com>, Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH 3/5] hwmon: (tmp102) Use maple tree register cache
Date: Sat, 10 Jun 2023 14:59:09 +0100 [thread overview]
Message-ID: <20230609-hwmon-maple-v1-3-8edacce86b28@kernel.org> (raw)
In-Reply-To: <20230609-hwmon-maple-v1-0-8edacce86b28@kernel.org>
The tmp102 is only capable of performing single register read and write
operations which means it gains no advantage from using a rbtree register
cache, convert it to using the more modern maple tree register cache
instead. This should be more efficient.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
drivers/hwmon/tmp102.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/tmp102.c b/drivers/hwmon/tmp102.c
index e271556efe0b..9563e1328b74 100644
--- a/drivers/hwmon/tmp102.c
+++ b/drivers/hwmon/tmp102.c
@@ -184,7 +184,7 @@ static const struct regmap_config tmp102_regmap_config = {
.writeable_reg = tmp102_is_writeable_reg,
.volatile_reg = tmp102_is_volatile_reg,
.val_format_endian = REGMAP_ENDIAN_BIG,
- .cache_type = REGCACHE_RBTREE,
+ .cache_type = REGCACHE_MAPLE,
.use_single_read = true,
.use_single_write = true,
};
--
2.30.2
next prev parent reply other threads:[~2023-06-10 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 13:59 [PATCH 0/5] hwmon: Update single register drivers to use " Mark Brown
2023-06-10 13:59 ` [PATCH 1/5] hwmon: (lm75) Use " Mark Brown
2023-06-10 13:59 ` [PATCH 2/5] hwmon: (lm95245) " Mark Brown
2023-06-10 13:59 ` Mark Brown [this message]
2023-06-10 13:59 ` [PATCH 4/5] hwmon: (tmp108) " Mark Brown
2023-06-10 13:59 ` [PATCH 5/5] hwmon: (tmp464) " Mark Brown
2023-06-10 14:15 ` [PATCH 0/5] hwmon: Update single register drivers to use " Guenter Roeck
2023-06-10 14:24 ` Mark Brown
2023-06-10 14:36 ` Guenter Roeck
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=20230609-hwmon-maple-v1-3-8edacce86b28@kernel.org \
--to=broonie@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®