[PATCH] ASoC: rt715: add vendor clear control register

[PATCH] ASoC: rt715: add vendor clear control register

[Jack Yu]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

Add vendor clear control register in readable register's
callback function. This prevents an access failure reported
in Intel CI tests.

Signed-off-by: Jack Yu <jack.yu@realtek.com>
---
 sound/soc/codecs/rt715-sdw.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sound/soc/codecs/rt715-sdw.c b/sound/soc/codecs/rt715-sdw.c
index 24b3443aeb02..ec255ada44e0 100644
--- a/sound/soc/codecs/rt715-sdw.c
+++ b/sound/soc/codecs/rt715-sdw.c
@@ -111,6 +111,7 @@ static bool rt715_readable_register(struct device *dev, unsigned int reg)
 	case 0x839d:
 	case 0x83a7:
 	case 0x83a9:
+	case 0x752001:
 	case 0x752039:
 		return true;
 	default:
-- 
2.34.1


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 5323 bytes --]

Re: [PATCH] ASoC: rt715: add vendor clear control register

[Pierre-Louis Bossart]

On 4/15/24 01:27, Jack Yu wrote:
> Add vendor clear control register in readable register's
> callback function. This prevents an access failure reported
> in Intel CI tests.
> 
> Signed-off-by: Jack Yu <jack.yu@realtek.com>

Closes: https://github.com/thesofproject/linux/issues/4860
Tested-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

Re: [PATCH] ASoC: rt715: add vendor clear control register

[Mark Brown]

On Mon, 15 Apr 2024 06:27:23 +0000, Jack Yu wrote:
> Add vendor clear control register in readable register's
> callback function. This prevents an access failure reported
> in Intel CI tests.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt715: add vendor clear control register
      commit: cebfbc89ae2552dbb58cd9b8206a5c8e0e6301e9

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