[PATCH] Mark the ADAU7118 reset register as volatile.
From: Chris Garren cdgarren@indesign-llc.com
Without this the previously written value was written to this reg, which caused the different configuration registers to be reset.
Signed-off-by: Chris Garren cdgarren@indesign-llc.com --- sound/soc/codecs/adau7118-i2c.c | 7 +++++++ 1 file changed, 7 insertions(+)
diff --git a/sound/soc/codecs/adau7118-i2c.c b/sound/soc/codecs/adau7118-i2c.c index a821136..aa7afb3 100644 --- a/sound/soc/codecs/adau7118-i2c.c +++ b/sound/soc/codecs/adau7118-i2c.c @@ -32,6 +32,12 @@ static const struct reg_default adau7118_reg_defaults[] = { { ADAU7118_REG_RESET, 0x00 }, };
+static bool adau7118_volatile(struct device *dev, unsigned int reg) +{ + return (reg == ADAU7118_REG_RESET); +} + + static const struct regmap_config adau7118_regmap_config = { .reg_bits = 8, .val_bits = 8, @@ -39,6 +45,7 @@ static const struct regmap_config adau7118_regmap_config = { .num_reg_defaults = ARRAY_SIZE(adau7118_reg_defaults), .cache_type = REGCACHE_RBTREE, .max_register = ADAU7118_REG_RESET, + .volatile_reg = adau7118_volatile, };
static int adau7118_probe_i2c(struct i2c_client *i2c,
On Mon, 4 May 2020 09:43:20 -0400, chris.d.garren@gmail.com wrote:
From: Chris Garren cdgarren@indesign-llc.com
Without this the previously written value was written to this reg, which caused the different configuration registers to be reset.
Signed-off-by: Chris Garren cdgarren@indesign-llc.com
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.7
Thanks!
[1/1] ASoC: adau7118: Mark the ADAU7118 reset register as volatile commit: f2b1e1cbd352129cfdbc1af52059482d74b4e81a
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
participants (2)
-
chris.d.garren＠gmail.com -
Mark Brown