[PATCH v2] ASoC: dt-bindings: rt5616: Convert to dtschema
![](https://secure.gravatar.com/avatar/a1fb6b1c0c7a92db08bb20d68823ee92.jpg?s=120&d=mm&r=g)
Convert the rt5616 audio CODEC bindings to DT schema
Signed-off-by: Bragatheswaran Manickavel bragathemanick0908@gmail.com --- V1 -> V2: Changes codec to audio-codec and added spacing above
.../bindings/sound/realtek,rt5616.yaml | 49 +++++++++++++++++++ .../devicetree/bindings/sound/rt5616.txt | 32 ------------ 2 files changed, 49 insertions(+), 32 deletions(-) create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt5616.yaml delete mode 100644 Documentation/devicetree/bindings/sound/rt5616.txt
diff --git a/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml b/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml new file mode 100644 index 000000000000..a387f802afd1 --- /dev/null +++ b/Documentation/devicetree/bindings/sound/realtek,rt5616.yaml @@ -0,0 +1,49 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/sound/realtek,rt5616.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Realtek rt5616 ALSA SoC audio codec driver + +description: | + Pins on the device (for linking into audio routes) for RT5616: + + * IN1P + * IN2P + * IN2N + * LOUTL + * LOUTR + * HPOL + * HPOR + +maintainers: + - Bard Liao bardliao@realtek.com + +allOf: + - $ref: dai-common.yaml# + +properties: + compatible: + const: realtek,rt5616 + + reg: + maxItems: 1 + +required: + - compatible + - reg + +unevaluatedProperties: false + +examples: + - | + i2c { + #address-cells = <1>; + #size-cells = <0>; + + audio-codec@1b { + compatible = "realtek,rt5616"; + reg = <0x1b>; + }; + }; diff --git a/Documentation/devicetree/bindings/sound/rt5616.txt b/Documentation/devicetree/bindings/sound/rt5616.txt deleted file mode 100644 index 540a4bf252e4..000000000000 --- a/Documentation/devicetree/bindings/sound/rt5616.txt +++ /dev/null @@ -1,32 +0,0 @@ -RT5616 audio CODEC - -This device supports I2C only. - -Required properties: - -- compatible : "realtek,rt5616". - -- reg : The I2C address of the device. - -Optional properties: - -- clocks: The phandle of the master clock to the CODEC. - -- clock-names: Should be "mclk". - -Pins on the device (for linking into audio routes) for RT5616: - - * IN1P - * IN2P - * IN2N - * LOUTL - * LOUTR - * HPOL - * HPOR - -Example: - -rt5616: codec@1b { - compatible = "realtek,rt5616"; - reg = <0x1b>; -};
![](https://secure.gravatar.com/avatar/ee1e7f40e65828eb76184367a6353704.jpg?s=120&d=mm&r=g)
On Sat, 30 Sep 2023 22:20:50 +0530, Bragatheswaran Manickavel wrote:
Convert the rt5616 audio CODEC bindings to DT schema
Signed-off-by: Bragatheswaran Manickavel bragathemanick0908@gmail.com
V1 -> V2: Changes codec to audio-codec and added spacing above
.../bindings/sound/realtek,rt5616.yaml | 49 +++++++++++++++++++ .../devicetree/bindings/sound/rt5616.txt | 32 ------------ 2 files changed, 49 insertions(+), 32 deletions(-) create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt5616.yaml delete mode 100644 Documentation/devicetree/bindings/sound/rt5616.txt
Reviewed-by: Rob Herring robh@kernel.org
![](https://secure.gravatar.com/avatar/d930951cb00393ecf9c3db3a56d78fa9.jpg?s=120&d=mm&r=g)
On Sat, 30 Sep 2023 22:20:50 +0530, Bragatheswaran Manickavel wrote:
Convert the rt5616 audio CODEC bindings to DT schema
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: rt5616: Convert to dtschema commit: 943bcc742ec4d7da4d26477f2188940ecad76569
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 (1)
-
Bragatheswaran Manickavel
-
Mark Brown
-
Rob Herring