ASoC: dt-bindings: rt1016: Convert to dtschema

Convert the RT1016 Stereo Audio Amplifier bindings to DT schema

---
 .../bindings/sound/realtek,rt1016.yaml        | 40 +++++++++++++++++++
 .../devicetree/bindings/sound/rt1016.txt      | 17 --------
 2 files changed, 40 insertions(+), 17 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt1016.yaml
 delete mode 100644 Documentation/devicetree/bindings/sound/rt1016.txt

new file mode 100644
index 000000000000..5287e9c9197e
@@ -0,0 +1,40 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/sound/realtek,rt1016.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Reaktek RT1016 Stereo Class D Audio Amplifier
+
+maintainers:
+  - [email protected]
+
+allOf:
+  - $ref: dai-common.yaml#
+
+properties:
+  compatible:
+    const: realtek,rt1016
+
+  reg:
+    maxItems: 1
+
+  "#sound-dai-cells":
+    const: 0
+
+required:
+  - compatible
+  - reg
+
+unevaluatedProperties: false
+
+examples:
+  - |
+    i2c {
+        #address-cells = <1>;
+        #size-cells = <0>;
+        codec@1a {
+            compatible = "realtek,rt1016";
+            reg = <0x1a>;
+        };
+    };

deleted file mode 100644
index 2310f8ff259b..000000000000
@@ -1,17 +0,0 @@
-RT1016 Stereo Class D Audio Amplifier
-
-This device supports I2C only.
-
-Required properties:
-
-- compatible : "realtek,rt1016".
-
-- reg : The I2C address of the device.
-
-
-Example:
-
-rt1016: codec@1a {
-	compatible = "realtek,rt1016";
-	reg = <0x1a>;
-};

2.34.1

Thank you, will keep that in mind.

Hi Mark,

Do I need to send the v2 by copying [email protected] into the patch?

I saw you already added him.

Regards,
Anup Sharma

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: rt1016: Convert to dtschema

      commit: d8b44d8df4d932db3d88b2e79c67ffbd2c72e4dd

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