Skip to contentSkip to conversation

ASoC: dt-bindings: samsung,tm2: Correct "audio-codec" constraints

PATCH In review Rob Herring 3 participants 3 messages Jan 24, 2024 – Jan 26, 2024

Subsystems (4)
lore
Share & tools
lore

Rob Herring

author maintainer
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: samsung,tm2: Correct "audio-codec" constraints

The "audio-codec" constraints define how many entries(2), but not the size of each entry. Each entry is a single phandle. Define the size with an inner 'items' list.

---
 Documentation/devicetree/bindings/sound/samsung,tm2.yaml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/sound/samsung,tm2.yaml +5 -2
index 760592599143..cbc7ba37362a 100644
@@ -25,8 +25,11 @@ properties:
     description: Phandles to the codecs.
     $ref: /schemas/types.yaml#/definitions/phandle-array
     items:
-      - description: Phandle to the WM5110 audio codec.
-      - description: Phandle to the HDMI transmitter node.
+      - items:
+          - description: Phandle to the WM5110 audio codec.
+      - items:
+          - description: Phandle to the HDMI transmitter node.
+
 
   samsung,audio-routing:
     description: |
Signature · 1 line
2.43.0
maintainer
#2 lore raw
In reply to Rob Herring
Quoted 5 lines · Rob Herring

The "audio-codec" constraints define how many entries(2), but not the size of each entry. Each entry is a single phandle. Define the size with an inner 'items' list.

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: samsung,tm2: Correct "audio-codec" constraints

      commit: 36553eb7785da18568de2b8ecafb3d80db1a0d6b

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