[PATCH] 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.
Signed-off-by: Rob Herring robh@kernel.org --- Documentation/devicetree/bindings/sound/samsung,tm2.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/samsung,tm2.yaml b/Documentation/devicetree/bindings/sound/samsung,tm2.yaml index 760592599143..cbc7ba37362a 100644 --- a/Documentation/devicetree/bindings/sound/samsung,tm2.yaml +++ b/Documentation/devicetree/bindings/sound/samsung,tm2.yaml @@ -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: |
On 24/01/2024 20:07, Rob Herring wrote:
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.
Signed-off-by: Rob Herring robh@kernel.org
Reviewed-by: Krzysztof Kozlowski krzysztof.kozlowski@linaro.org
Best regards, Krzysztof
On Wed, 24 Jan 2024 13:07:53 -0600, Rob Herring wrote:
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
participants (3)
-
Krzysztof Kozlowski -
Mark Brown -
Rob Herring