[PATCH] ASoC: mediatek: mt8186: add AFE_DAC_CON0 to volatile register list

Chunxu Li posted 1 patch 1 year, 8 months ago
sound/soc/mediatek/mt8186/mt8186-afe-pcm.c | 1 +
1 file changed, 1 insertion(+)
[PATCH] ASoC: mediatek: mt8186: add AFE_DAC_CON0 to volatile register list
Posted by Chunxu Li 1 year, 8 months ago
Mark AFE_DAC_CON0 as volatile since DSP firmware will access this
register too.

Signed-off-by: Chunxu Li <chunxu.li@mediatek.com>
---
 sound/soc/mediatek/mt8186/mt8186-afe-pcm.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sound/soc/mediatek/mt8186/mt8186-afe-pcm.c b/sound/soc/mediatek/mt8186/mt8186-afe-pcm.c
index d7e94e6a19c7..41172a82103e 100644
--- a/sound/soc/mediatek/mt8186/mt8186-afe-pcm.c
+++ b/sound/soc/mediatek/mt8186/mt8186-afe-pcm.c
@@ -2395,6 +2395,7 @@ static bool mt8186_is_volatile_reg(struct device *dev, unsigned int reg)
 	case AUDIO_TOP_CON1:	/* reg bit controlled by CCF */
 	case AUDIO_TOP_CON2:
 	case AUDIO_TOP_CON3:
+	case AFE_DAC_CON0:
 	case AFE_DL1_CUR_MSB:
 	case AFE_DL1_CUR:
 	case AFE_DL1_END:
-- 
2.25.1
Re: [PATCH] ASoC: mediatek: mt8186: add AFE_DAC_CON0 to volatile register list
Posted by Mark Brown 1 year, 8 months ago
On Tue, 10 Jan 2023 17:26:23 +0800, Chunxu Li wrote:
> Mark AFE_DAC_CON0 as volatile since DSP firmware will access this
> register too.
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASoC: mediatek: mt8186: add AFE_DAC_CON0 to volatile register list
      commit: 42fc858cc7e3f9e7a5762b29f9daaf23a15e45ef

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