The primary purpose behind this series is to convert the Mediatek
MT6358 Audio Codec dt-binding documentation from txt to dt-schema.
Additionally, it fixes the dts for some mediatek boards which were using
this dt-binding but were missing the required `Avdd-supply` property.
I have also updated the parent PMIC txt documentation to
reference this binding. I have not added any new examples as the older
example already has a codec node.
I have tested my patches against `mt8186-corsola-steelix-sku131072.dts`,
`mt8186-corsola-steelix-sku131073.dts`, `mt8183-evb.dts`, and
`mt8183-pumpkin.dts`.
To: Liam Girdwood <lgirdwood@gmail.com>
To: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
To: Conor Dooley <conor+dt@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Lee Jones <lee@kernel.org>
Cc: linux-sound@vger.kernel.org
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-mediatek@lists.infradead.org
Signed-off-by: Kartik Agarwala <agarwala.kartik@gmail.com>
Changes for v2:
Fix problems with the `compatible` field
Add missing required properties
Previous Versions:
v1: https://lore.kernel.org/all/20240518081621.63386-1-agarwala.kartik@gmail.com/
---
Kartik Agarwala (3):
ASoC: dt-bindings: mt6358: Convert to dtschema
arm64: dts: mediatek: Add missing Avdd-supply property for mt6358codec
dt-bindings: mfd: mt6397: Add reference for mediatek,mt6358-sound
Documentation/devicetree/bindings/mfd/mt6397.txt | 1 +
.../devicetree/bindings/sound/mediatek,mt6358.yaml | 51 ++++++++++++++++++++++
Documentation/devicetree/bindings/sound/mt6358.txt | 26 -----------
arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 4 ++
arch/arm64/boot/dts/mediatek/mt8183-pumpkin.dts | 4 ++
5 files changed, 60 insertions(+), 26 deletions(-)
---
base-commit: 617f9a0a70e8bc27ef0343f3abac1faeba07cb71
change-id: 20240606-mt6358-e6fff7ed5747
Best regards,
--
Kartik Agarwala <agarwala.kartik@gmail.com>