Skip to contentSkip to conversation

dt-bindings: ti,pcm1681: Convert to dtschema

PATCH In review Animesh Agarwal 3 participants 3 messages Apr 6, 2024 – Apr 8, 2024

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

PATCH v2 1/1 dt-bindings: ti,pcm1681: Convert to dtschema

Convert the Texas Instruments PCM1681 bindings to DT schema. Make bindings complete by adding #sound-dai-cells.

---
Changes in v2:
- Added existing maintainers to the list of maintainers.
- Added #sound-dai-cells, $ref to dai-common and unevaluatedProperties: false.
- Added "audio-codec" in example.

---
 .../devicetree/bindings/sound/ti,pcm1681.txt  | 15 -------
 .../devicetree/bindings/sound/ti,pcm1681.yaml | 43 +++++++++++++++++++
 2 files changed, 43 insertions(+), 15 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/sound/ti,pcm1681.txt
 create mode 100644 Documentation/devicetree/bindings/sound/ti,pcm1681.yaml
Documentation/devicetree/bindings/sound/ti,pcm1681.txt deleted +0 -15
deleted file mode 100644
index 4df17185ab80..000000000000
@@ -1,15 +0,0 @@
-Texas Instruments PCM1681 8-channel PWM Processor
-
-Required properties:
-
- - compatible:		Should contain "ti,pcm1681".
- - reg:			The i2c address. Should contain <0x4c>.
-
-Examples:
-
-	i2c_bus {
-		pcm1681@4c {
-			compatible = "ti,pcm1681";
-			reg = <0x4c>;
-		};
-	};
Documentation/devicetree/bindings/sound/ti,pcm1681.yaml new file +43 -0

43 lines not on this page · raw message

Signature · 1 line
2.44.0
maintainer
#2 lore raw
In reply to Animesh Agarwal
Quoted 4 lines · Animesh Agarwal

Convert the Texas Instruments PCM1681 bindings to DT schema. Make bindings complete by adding #sound-dai-cells.

Applied to

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

Thanks!

[1/1] dt-bindings: ti,pcm1681: Convert to dtschema

      commit: 8167bd1c8a45c289316417cf938bcd8ceec24fd5

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