Skip to contentSkip to conversation

ASoC: dt-bindings: mediatek: Fix MT8186 child node names

PATCH In review Rob Herring (Arm) 2 participants 2 messages Nov 2

Subsystems (4)
lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: mediatek: Fix MT8186 child node names

Use 'playback-codecs' instead of 'speaker-codecs' in the legacy-property exclusion for both MT8186 sound card bindings. This appears to be a copy-n-paste error as 'playback-codecs' is the name defined by these bindings and consumed by the driver.

---
 .../bindings/sound/mt8186-mt6366-da7219-max98357.yaml           | 2 +-
 .../devicetree/bindings/sound/mt8186-mt6366-rt1019-rt5682s.yaml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/sound/mt8186-mt6366-da7219-max98357.yaml +1 -1
index 037f21443ad1..922dfdf55a66 100644
@@ -145,7 +145,7 @@ if:
 then:
   properties:
     headset-codec: false
-    speaker-codecs: false
+    playback-codecs: false
 
 examples:
   - |
Documentation/devicetree/bindings/sound/mt8186-mt6366-rt1019-rt5682s.yaml +1 -1
index ed93f18ef985..ddc7a0ce69be 100644
@@ -144,7 +144,7 @@ if:
 then:
   properties:
     headset-codec: false
-    speaker-codecs: false
+    playback-codecs: false
 
 examples:
   - |
Signature · 1 line
2.53.0
maintainer
#1 lore raw
Quoted 1 line · Rob Herring (Arm)

ASoC: dt-bindings: mediatek: Fix MT8186 child node names

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: mediatek: Fix MT8186 child node names

      https://git.kernel.org/broonie/sound/c/25a38dd4ff95

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