Convert the ALC5632 audio codec bindings to DT schema.
Signed-off-by: Saalim Quadri <[email protected]>
---
Changes:
V1 -> V2: Use correct node name
V2 -> V3: Add correct maintainer name
V3 -> V4: Drop alc5632 label name
.../devicetree/bindings/sound/alc5632.txt | 43 -------------
.../bindings/sound/realtek,alc5632.yaml | 63 +++++++++++++++++++
2 files changed, 63 insertions(+), 43 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/sound/alc5632.txt
create mode 100644 Documentation/devicetree/bindings/sound/realtek,alc5632.yaml
diff --git a/Documentation/devicetree/bindings/sound/alc5632.txt b/Documentation/devicetree/bindings/sound/alc5632.txt
deleted file mode 100644
index ffd886d110bd..000000000000
--- a/Documentation/devicetree/bindings/sound/alc5632.txt
+++ /dev/null
@@ -1,43 +0,0 @@
-ALC5632 audio CODEC
-
-This device supports I2C only.
-
-Required properties:
-
- - compatible : "realtek,alc5632"
-
- - reg : the I2C address of the device.
-
- - gpio-controller : Indicates this device is a GPIO controller.
-
- - #gpio-cells : Should be two. The first cell is the pin number and the
- second cell is used to specify optional parameters (currently unused).
-
-Pins on the device (for linking into audio routes):
-
- * SPK_OUTP
- * SPK_OUTN
- * HP_OUT_L
- * HP_OUT_R
- * AUX_OUT_P
- * AUX_OUT_N
- * LINE_IN_L
- * LINE_IN_R
- * PHONE_P
- * PHONE_N
- * MIC1_P
- * MIC1_N
- * MIC2_P
- * MIC2_N
- * MICBIAS1
- * DMICDAT
-
-Example:
-
-alc5632: alc5632@1e {
- compatible = "realtek,alc5632";
- reg = <0x1a>;
-
- gpio-controller;
- #gpio-cells = <2>;
-};
diff --git a/Documentation/devicetree/bindings/sound/realtek,alc5632.yaml b/Documentation/devicetree/bindings/sound/realtek,alc5632.yaml
new file mode 100644
index 000000000000..fb05988ff7ea
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/realtek,alc5632.yaml
@@ -0,0 +1,63 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/sound/realtek,alc5632.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ALC5632 audio CODEC
+
+description: |
+ Pins on the device (for linking into audio routes):
+ * SPK_OUTP
+ * SPK_OUTN
+ * HP_OUT_L
+ * HP_OUT_R
+ * AUX_OUT_P
+ * AUX_OUT_N
+ * LINE_IN_L
+ * LINE_IN_R
+ * PHONE_P
+ * PHONE_N
+ * MIC1_P
+ * MIC1_N
+ * MIC2_P
+ * MIC2_N
+ * MICBIAS1
+ * DMICDAT
+
+maintainers:
+ - Leon Romanovsky <[email protected]>
+
+properties:
+ compatible:
+ const: realtek,alc5632
+
+ reg:
+ maxItems: 1
+
+ '#gpio-cells':
+ const: 2
+
+ gpio-controller: true
+
+required:
+ - compatible
+ - reg
+ - '#gpio-cells'
+ - gpio-controller
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ codec@1a {
+ compatible = "realtek,alc5632";
+ reg = <0x1a>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ };
+ };
--
2.34.1
On 27/03/2023 23:16, Saalim Quadri wrote:
> Convert the ALC5632 audio codec bindings to DT schema.
>
> Signed-off-by: Saalim Quadri <[email protected]>
> ---
I wanted to review it but for some reason you keep ignoring my comment.
So one more time:
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Is there something not clear about my request above?
Best regards,
Krzysztof
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
Apologies but, this is the output of get_maintainers.pl, is there something that I missed?
I am currently working no 6.3-rc3 as my base kernel.
> saalim@pavilion:~/workspace/linux$ scripts/get_maintainer.pl Documentation/devicetree/bindings/sound/alc5632.txt
> Liam Girdwood <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
> Mark Brown <[email protected]> (supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
> Rob Herring <[email protected]> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> Krzysztof Kozlowski <[email protected]> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> [email protected] (moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...)
> [email protected] (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> [email protected] (open list)
Thank you,
Saalim
On 28/03/2023 10:33, Saalim Quadri wrote:
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC. It might happen, that command when run on an older
>> kernel, gives you outdated entries. Therefore please be sure you base
>> your patches on recent Linux kernel.
>
> Apologies but, this is the output of get_maintainers.pl, is there something that I missed?
>
> I am currently working no 6.3-rc3 as my base kernel.
>
>> saalim@pavilion:~/workspace/linux$ scripts/get_maintainer.pl Documentation/devicetree/bindings/sound/alc5632.txt
It's not the correct way to run it. It should not even work at all -
there is no alc5632.txt file, so I really doubt you run it exactly like
this. Anyway:
git format-patch -1 -5
scripts/get_maintainer.pl v5-*
and you will get a bit different results.
Best regards,
Krzysztof
> git format-patch -1 -5
> scripts/get_maintainer.pl v5-*
> and you will get a bit different results.
There was a new entry this time, while the rest of the output was same.
Leon Romanovsky <[email protected]> (in file)
I added him as a CC here
Thank you,
Saalim
On Tue, 28 Mar 2023 02:46:29 +0530, Saalim Quadri wrote:
> Convert the ALC5632 audio codec bindings to DT schema.
>
>
Applied to
broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: alc5632: Convert to dtschema
commit: 0b57a2d87b4de2a1f01edaf3b00b3d1939792948
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