Skip to contentSkip to conversation

ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile

PATCH In review yr.yang 4 participants 4 messages Aug 1, 2024 – Aug 15, 2024

Subsystems (3)
lore
Share & tools
lore

yr.yang

author
#0 lore raw

PATCH v2 1/1 ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile

From: YR Yang <[email protected]>

Add AFE Control Register 0 to the volatile_register. AFE_DAC_CON0 can be modified by both the SOF and ALSA drivers. If this register is read and written in cache mode, the cached value might not reflect the actual value when the register is modified by another driver. It can cause playback or capture failures. Therefore, it is necessary to add AFE_DAC_CON0 to the list of volatile registers.

---
Changes in v2:
- Modify commit message.
- Link to v1: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

---
 sound/soc/mediatek/mt8188/mt8188-afe-pcm.c | 1 +
 1 file changed, 1 insertion(+)
sound/soc/mediatek/mt8188/mt8188-afe-pcm.c +1 -0
index ccb6c1f3adc7..73e5c63aeec8 100644
@@ -2748,6 +2748,7 @@ static bool mt8188_is_volatile_reg(struct device *dev, unsigned int reg)
 	case AFE_ASRC12_NEW_CON9:
 	case AFE_LRCK_CNT:
 	case AFE_DAC_MON0:
+	case AFE_DAC_CON0:
 	case AFE_DL2_CUR:
 	case AFE_DL3_CUR:
 	case AFE_DL6_CUR:
Signature · 1 line
2.34.1
Reviewed-by on v2 1/1
#1 lore raw

Hi YR,

Quoted 11 lines · yr.yang

From: YR Yang <[email protected]>

Add AFE Control Register 0 to the volatile_register. AFE_DAC_CON0 can be modified by both the SOF and ALSA drivers. If this register is read and written in cache mode, the cached value might not reflect the actual value when the register is modified by another driver. It can cause playback or capture failures. Therefore, it is necessary to add AFE_DAC_CON0 to the list of volatile registers.

For this patch for MT8188:

And a side question: is the same also required in mt8195-afe-pcm.c? Their volatile register sets look almost identical (except MT8195 has some extra lines).

Regards,
Fei

Quoted 24 lines

---
Changes in v2:
- Modify commit message.
- Link to v1: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

---
 sound/soc/mediatek/mt8188/mt8188-afe-pcm.c | 1 +
 1 file changed, 1 insertion(+)
sound/soc/mediatek/mt8188/mt8188-afe-pcm.c +1 -1
index ccb6c1f3adc7..73e5c63aeec8 100644
@@ -2748,6 +2748,7 @@ static bool mt8188_is_volatile_reg(struct device *dev, unsigned int reg)
        case AFE_ASRC12_NEW_CON9:
        case AFE_LRCK_CNT:
        case AFE_DAC_MON0:
+       case AFE_DAC_CON0:
        case AFE_DL2_CUR:
        case AFE_DL3_CUR:
        case AFE_DL6_CUR:
--

2.34.1

Reviewed-by on v2 1/1
#2 lore raw
In reply to yr.yang
Quoted 10 lines · yr.yang

From: YR Yang <[email protected]>

Add AFE Control Register 0 to the volatile_register. AFE_DAC_CON0 can be modified by both the SOF and ALSA drivers. If this register is read and written in cache mode, the cached value might not reflect the actual value when the register is modified by another driver. It can cause playback or capture failures. Therefore, it is necessary to add AFE_DAC_CON0 to the list of volatile registers.

Quoted 3 lines

---

Thanks,
Trevor

maintainer
#3 lore raw
In reply to yr.yang
Quoted 8 lines · yr.yang

Add AFE Control Register 0 to the volatile_register. AFE_DAC_CON0 can be modified by both the SOF and ALSA drivers. If this register is read and written in cache mode, the cached value might not reflect the actual value when the register is modified by another driver. It can cause playback or capture failures. Therefore, it is necessary to add AFE_DAC_CON0 to the list of volatile registers.

[...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile

      commit: ff9f065318e17a1a97981d9e535fcfc6ce5d5614

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