[PATCH] regulator: rtmv20: Add missing regcache cache only before marked as dirty

[PATCH] regulator: rtmv20: Add missing regcache cache only before marked as dirty

[cy_huang]

From: ChiYuan Huang <cy_huang@richtek.com>

Add missing regcache cache only before masked as dirty.

Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
---
 drivers/regulator/rtmv20-regulator.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/regulator/rtmv20-regulator.c b/drivers/regulator/rtmv20-regulator.c
index 1075b10..0a07598 100644
--- a/drivers/regulator/rtmv20-regulator.c
+++ b/drivers/regulator/rtmv20-regulator.c
@@ -321,6 +321,7 @@ static int rtmv20_probe(struct i2c_client *i2c)
 	 * keep in shutdown mode to minimize the current consumption
 	 * and also mark regcache as dirty
 	 */
+	regcache_cache_only(priv->regmap, true);
 	regcache_mark_dirty(priv->regmap);
 	gpiod_set_value(priv->enable_gpio, 0);
 
-- 
2.7.4

Re: [PATCH] regulator: rtmv20: Add missing regcache cache only before marked as dirty

[Mark Brown]

On Wed, 30 Sep 2020 18:18:52 +0800, cy_huang wrote:
> Add missing regcache cache only before masked as dirty.

Applied to

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

Thanks!

[1/1] regulator: rtmv20: Add missing regcache cache only before marked as dirty
      commit: 6228cc8aed9e51afa56727b11001b37913e4dda6

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