Skip to contentSkip to conversation

ASoC: rt5682: remove connection with LDO2 in DAPM graph

PATCH In review [email protected] 2 participants 2 messages Jan 21, 2021

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

PATCH 1/1 ASoC: rt5682: remove connection with LDO2 in DAPM graph

From: Shuming Fan <[email protected]>

The application circuit shall provide MICVDD power.
In default, the codec driver doesn't need to enable LDO2.
In case, a board wants to use VBAT for micbias,
it should add a DAPM route which IN1P connects with LDO2 in the machine driver. e.g. { "IN1P", NULL, "LDO2" },

---
 sound/soc/codecs/rt5682.c | 2 --
 1 file changed, 2 deletions(-)
sound/soc/codecs/rt5682.c +0 -2
index 42ad5bea86b5..185906d6d4e0 100644
@@ -1854,8 +1854,6 @@ static const struct snd_soc_dapm_route rt5682_dapm_routes[] = {
 
 	{"CLKDET SYS", NULL, "CLKDET"},
 
-	{"IN1P", NULL, "LDO2"},
-
 	{"BST1 CBJ", NULL, "IN1P"},
 
 	{"RECMIX1L", "CBJ Switch", "BST1 CBJ"},
Signature · 1 line
2.29.0
maintainer
#1 lore raw
Quoted 5 lines · On Thu, 21 Jan 2021 18:03:53 +0800, [email protected] wrote:

The application circuit shall provide MICVDD power.
In default, the codec driver doesn't need to enable LDO2.
In case, a board wants to use VBAT for micbias,
it should add a DAPM route which IN1P connects with LDO2 in the machine driver. e.g. { "IN1P", NULL, "LDO2" },

Applied to

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

Thanks!

[1/1] ASoC: rt5682: remove connection with LDO2 in DAPM graph

      commit: 06c8456753f6fc89ff5894cc8cca24b1ac92a5d6

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