mbox series

[v2,0/2] ASoC: dt-bindings: convert qcom sound bindings to yaml

Message ID 20240710113833.39859-1-rayyan.ansari@linaro.org
Headers show
Series ASoC: dt-bindings: convert qcom sound bindings to yaml | expand

Message

Rayyan Ansari July 10, 2024, 11:36 a.m. UTC
Hi,
These patches convert the remaining plain text bindings for Qualcomm
sound drivers to dt schema, so device trees can be validated against
them.

v1: https://lore.kernel.org/all/20240709152808.155405-1-rayyan.ansari@linaro.org/

Thanks,
Rayyan

Rayyan Ansari (2):
  ASoC: dt-bindings: qcom,msm8916-wcd-digital-codec: convert to dtschema
  ASoC: dt-bindings: qcom,apq8096-sndcard: use dtschema

 .../bindings/sound/qcom,apq8096.txt           | 128 ------------------
 .../sound/qcom,msm8916-wcd-digital-codec.yaml |  55 ++++++++
 .../sound/qcom,msm8916-wcd-digital.txt        |  20 ---
 .../bindings/sound/qcom,sm8250.yaml           |   1 +
 4 files changed, 56 insertions(+), 148 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/sound/qcom,apq8096.txt
 create mode 100644 Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-digital-codec.yaml
 delete mode 100644 Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-digital.txt

Comments

Mark Brown July 11, 2024, 1:10 a.m. UTC | #1
On Wed, 10 Jul 2024 12:36:05 +0100, Rayyan Ansari wrote:
> These patches convert the remaining plain text bindings for Qualcomm
> sound drivers to dt schema, so device trees can be validated against
> them.
> 
> v1: https://lore.kernel.org/all/20240709152808.155405-1-rayyan.ansari@linaro.org/
> 
> Thanks,
> Rayyan
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: qcom,msm8916-wcd-digital-codec: convert to dtschema
      commit: 054ac9c97c7d9eb55f471fc6f019b654d17332a7
[2/2] ASoC: dt-bindings: qcom,apq8096-sndcard: use dtschema
      commit: 3cbda25e2db28b4352c73d4167f0dab10049ea54

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