On 09/04/2024 10:50, Shengjiu Wang wrote: > Convert the imx-audio-spdif binding to YAML. > > When testing dtbs_check, found below compatible strings > are not listed in document: > > fsl,imx-sabreauto-spdif > fsl,imx6sx-sdb-spdif > > So add them in yaml file to pass the test. > > Signed-off-by: Shengjiu Wang <shengjiu.wang@xxxxxxx> > --- > .../bindings/sound/fsl,imx-audio-spdif.yaml | 67 +++++++++++++++++++ > .../bindings/sound/imx-audio-spdif.txt | 36 ---------- > 2 files changed, 67 insertions(+), 36 deletions(-) > create mode 100644 Documentation/devicetree/bindings/sound/fsl,imx-audio-spdif.yaml > delete mode 100644 Documentation/devicetree/bindings/sound/imx-audio-spdif.txt > > diff --git a/Documentation/devicetree/bindings/sound/fsl,imx-audio-spdif.yaml b/Documentation/devicetree/bindings/sound/fsl,imx-audio-spdif.yaml > new file mode 100644 > index 000000000000..fec008ffae43 > --- /dev/null > +++ b/Documentation/devicetree/bindings/sound/fsl,imx-audio-spdif.yaml > @@ -0,0 +1,67 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/sound/fsl,imx-audio-spdif.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Freescale i.MX audio complex with S/PDIF transceiver > + > +maintainers: > + - Shengjiu Wang <shengjiu.wang@xxxxxxx> > + > +properties: > + compatible: > + oneOf: > + - items: > + - enum: > + - fsl,imx-sabreauto-spdif > + - fsl,imx6sx-sdb-spdif > + - enum: > + - fsl,imx-audio-spdif If there is going to be any new version/resend: This one should be const, not enum. Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> --- This is an automated instruction, just in case, because many review tags are being ignored. If you know the process, you can skip it (please do not feel offended by me posting it here - no bad intentions intended). If you do not know the process, here is a short explanation: Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions, under or above your Signed-off-by tag. Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply. https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577 Best regards, Krzysztof
