[PATCH] ASoC: dt-bindings: microchip,sama7g5-spdifrx: Add common DAI reference
Update the spdifrx yaml file to reference the dai-common.yaml schema, enabling the use of the 'sound-name-prefix' property
Signed-off-by: Andrei Simion andrei.simion@microchip.com --- .../devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml b/Documentation/devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml index 2f43c684ab88..7fbab5871be4 100644 --- a/Documentation/devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml +++ b/Documentation/devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml @@ -13,6 +13,9 @@ description: The Microchip Sony/Philips Digital Interface Receiver is a serial port compliant with the IEC-60958 standard.
+allOf: + - $ref: dai-common.yaml# + properties: "#sound-dai-cells": const: 0 @@ -53,7 +56,7 @@ required: - dmas - dma-names
-additionalProperties: false +unevaluatedProperties: false
examples: - |
base-commit: 6708132e80a2ced620bde9b9c36e426183544a23
On Tue, 10 Sep 2024 11:22:03 +0300, Andrei Simion wrote:
Update the spdifrx yaml file to reference the dai-common.yaml schema, enabling the use of the 'sound-name-prefix' property
Signed-off-by: Andrei Simion andrei.simion@microchip.com
.../devicetree/bindings/sound/microchip,sama7g5-spdifrx.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
Acked-by: Rob Herring (Arm) robh@kernel.org
On Tue, 10 Sep 2024 11:22:03 +0300, Andrei Simion wrote:
Update the spdifrx yaml file to reference the dai-common.yaml schema, enabling the use of the 'sound-name-prefix' property
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: microchip,sama7g5-spdifrx: Add common DAI reference commit: 448aa89af07b83be84a58155c60001743342fca0
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)
-
Andrei Simion -
Mark Brown -
Rob Herring (Arm)