[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJbbDiOAr5-3_JwVMWxdkeGRoPYZuc_8fHp_iGEvH7AWA@mail.gmail.com>
Date: Mon, 20 Sep 2021 07:57:12 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Sameer Pujar <spujar@...dia.com>
Cc: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Thierry Reding <thierry.reding@...il.com>,
Jon Hunter <jonathanh@...dia.com>,
Stephan Gerhold <stephan@...hold.net>,
Jerome Brunet <jbrunet@...libre.com>,
Linux-ALSA <alsa-devel@...a-project.org>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-tegra <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] ASoC: Use schema reference for sound-name-prefix
On Fri, Sep 3, 2021 at 11:36 AM Sameer Pujar <spujar@...dia.com> wrote:
>
> Use schema reference for 'sound-name-prefix' property wherever
> necessary.
>
> Signed-off-by: Sameer Pujar <spujar@...dia.com>
> Cc: Jerome Brunet <jbrunet@...libre.com>
> Cc: Stephan Gerhold <stephan@...hold.net>
> Cc: Rob Herring <robh+dt@...nel.org>
> Reviewed-by: Jerome Brunet <jbrunet@...libre.com>
> Reviewed-by: Rob Herring <robh@...nel.org>
> ---
[...]
> diff --git a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
> index ffb8fcf..68e5ad2 100644
> --- a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
> +++ b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
> @@ -9,6 +9,9 @@ title: NXP/Goodix TFA989X (TFA1) Audio Amplifiers
> maintainers:
> - Stephan Gerhold <stephan@...hold.net>
>
> +allOf:
> + - $ref: name-prefix.yaml#
> +
> properties:
> compatible:
> enum:
> @@ -21,12 +24,6 @@ properties:
> '#sound-dai-cells':
> const: 0
>
> - sound-name-prefix:
You can't remove the property. This is now a warning in linux-next:
Documentation/devicetree/bindings/sound/nxp,tfa989x.example.dt.yaml:
audio-codec@34: 'sound-name-prefix' does not match any of the regexes:
'pinctrl-[0-9]+'
From schema: /builds/robherring/linux-dt/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
Documentation/devicetree/bindings/sound/nxp,tfa989x.example.dt.yaml:
audio-codec@36: 'sound-name-prefix' does not match any of the regexes:
'pinctrl-[0-9]+'
From schema: /builds/robherring/linux-dt/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
Just 'sound-name-prefix: true' is fine
> - $ref: /schemas/types.yaml#/definitions/string
> - description:
> - Used as prefix for sink/source names of the component. Must be a
> - unique string among multiple instances of the same component.
> -
> vddd-supply:
> description: regulator phandle for the VDDD power supply.
>
> diff --git a/Documentation/devicetree/bindings/sound/rt5659.txt b/Documentation/devicetree/bindings/sound/rt5659.txt
> index c473df5..013f534 100644
> --- a/Documentation/devicetree/bindings/sound/rt5659.txt
> +++ b/Documentation/devicetree/bindings/sound/rt5659.txt
> @@ -42,7 +42,7 @@ Optional properties:
> - realtek,ldo1-en-gpios : The GPIO that controls the CODEC's LDO1_EN pin.
> - realtek,reset-gpios : The GPIO that controls the CODEC's RESET pin.
>
> -- sound-name-prefix: Please refer to name-prefix.txt
> +- sound-name-prefix: Please refer to name-prefix.yaml
>
> - ports: A Codec may have a single or multiple I2S interfaces. These
> interfaces on Codec side can be described under 'ports' or 'port'.
> diff --git a/Documentation/devicetree/bindings/sound/simple-audio-mux.yaml b/Documentation/devicetree/bindings/sound/simple-audio-mux.yaml
> index 5986d1f..c597d9d 100644
> --- a/Documentation/devicetree/bindings/sound/simple-audio-mux.yaml
> +++ b/Documentation/devicetree/bindings/sound/simple-audio-mux.yaml
> @@ -13,6 +13,9 @@ description: |
> Simple audio multiplexers are driven using gpios, allowing to select which of
> their input line is connected to the output line.
>
> +allOf:
> + - $ref: name-prefix.yaml#
> +
> properties:
> compatible:
> const: simple-audio-mux
> @@ -21,12 +24,6 @@ properties:
> description: |
> GPIOs used to select the input line.
>
> - sound-name-prefix:
Here too, but I guess we don't have any example to throw a warning?
Powered by blists - more mailing lists