Skip to contentSkip to conversation

ASoC: rt5645: Make the Kconfig symbol user selectable

PATCH In review Rudi Heitbaum 2 participants 2 messages Aug 3

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ASoC: rt5645: Make the Kconfig symbol user selectable

SND_SOC_RT5645 has no prompt, so it can only be turned on by a machine driver that selects it. Every such driver is x86, MediaTek or Rockchip, which leaves the codec unreachable on any other platform.

The part has a devicetree binding of its own, Documentation/devicetree/bindings/sound/realtek,rt5645.yaml, and nothing in the driver is machine specific, so a board that describes it with simple-audio-card or audio-graph-card should be able to build it. Today there is no configuration in which that is possible.

Give the symbol a prompt, matching SND_SOC_RT5640 immediately above it. The machine drivers that select it are unaffected.

---
 sound/soc/codecs/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/Kconfig +1 -1
index 252f683be3c1..d43475a63ac2 100644
@@ -1856,7 +1856,7 @@ config SND_SOC_RT5640
 	depends on I2C
 
 config SND_SOC_RT5645
-	tristate
+	tristate "Realtek RT5645/RT5650 Codec"
 	depends on I2C
 
 config SND_SOC_RT5651
Signature · 1 line
2.53.0
maintainer
#1 lore raw
Quoted 1 line · Rudi Heitbaum

ASoC: rt5645: Make the Kconfig symbol user selectable

Applied to

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

Thanks!

[1/1] ASoC: rt5645: Make the Kconfig symbol user selectable

      https://git.kernel.org/broonie/sound/c/588852647b81

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