Skip to contentSkip to conversation

regulator: tps6287x-regulator: Enable REGCACHE_MAPLE

PATCH In review Jisheng Zhang 2 participants 2 messages Jun 29, 2025 – Jun 30, 2025 Voltage and current regulator framework

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: tps6287x-regulator: Enable REGCACHE_MAPLE

Enable regmap cache to reduce i2c transactions and corresponding interrupts if regulator is accessed frequently.

---
 drivers/regulator/tps6287x-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)
drivers/regulator/tps6287x-regulator.c +7 -0
index c0f5f0a186a3..7b7d3ae39206 100644
@@ -27,10 +27,17 @@
 #define TPS6287X_CTRL3		0x03
 #define TPS6287X_STATUS		0x04
 
+static bool tps6287x_volatile_reg(struct device *dev, unsigned int reg)
+{
+	return reg == TPS6287X_STATUS;
+}
+
 static const struct regmap_config tps6287x_regmap_config = {
 	.reg_bits = 8,
 	.val_bits = 8,
 	.max_register = TPS6287X_STATUS,
+	.cache_type = REGCACHE_MAPLE,
+	.volatile_reg = tps6287x_volatile_reg,
 };
 
 static const struct linear_range tps6287x_voltage_ranges[] = {
Signature · 1 line
2.49.0
maintainer
#1 lore raw
Quoted 4 lines · Jisheng Zhang

Enable regmap cache to reduce i2c transactions and corresponding interrupts if regulator is accessed frequently.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: tps6287x-regulator: Enable REGCACHE_MAPLE

      commit: b402dfe84057e376b39c8adadeb65ad51aaffeb4

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark