ASoC: dt-bindings: wm8523: Convert to dtschema

Convert the WM8523 audio CODEC bindings to DT schema

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

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

deleted file mode 100644
index f3a6485f4b8a..000000000000
@@ -1,16 +0,0 @@
-WM8523 audio CODEC
-
-This device supports I2C only.
-
-Required properties:
-
-  - compatible : "wlf,wm8523"
-
-  - reg : the I2C address of the device.
-
-Example:
-
-wm8523: codec@1a {
-	compatible = "wlf,wm8523";
-	reg = <0x1a>;
-};

2.34.1

At a minimum all of these devices should have separate regulator specifications should they ever grow regulator support (and ideally would have regulators specified in the binding from the get go).

There's also no reason to restrict simple CODECs to a particular manufacturer...

Hi,

Having a single file for other manufacturers, wouldn't that might cause issues with finding them?

Kind Regards,

Saalim

Good point. The bindings are incomplete that's why they look so similar. Therefore maybe we should not merge them, just like we do not add non-trivial-devices to trivial-devices schema, just because device is incomplete.

True, we could extend it to other brands.

Best regards,
Krzysztof

Hi,

I will check if there are other bindings under wm as well and squash them up into one.

Kind Regards,

Saalim

Applied to

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

Thanks!

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

      commit: 3e5f79723dc3f22fed30ba5a559db11b53b632ae

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