Skip to content

Commit

Permalink
ASoC: Fix warning related to 'sound-name-prefix' binding
Browse files Browse the repository at this point in the history
commit 82d3ec1 ("ASoC: Use schema reference for sound-name-prefix")
added name-prefix.yaml schema and the same reference was used in couple
of other schemas. But this is causing following warning and the same is
fixed in current patch.

 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: 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: Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml

Fixes: 82d3ec1 ("ASoC: Use schema reference for sound-name-prefix")
Reported-by: Rob Herring <[email protected]>
Suggested-by: Rob Herring <[email protected]>
Signed-off-by: Sameer Pujar <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
  • Loading branch information
pujars authored and broonie committed Sep 21, 2021
1 parent b5377a7 commit 013148f
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 0 deletions.
2 changes: 2 additions & 0 deletions Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ properties:
'#sound-dai-cells':
const: 0

sound-name-prefix: true

vddd-supply:
description: regulator phandle for the VDDD power supply.

Expand Down
2 changes: 2 additions & 0 deletions Documentation/devicetree/bindings/sound/simple-audio-mux.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ properties:
description: |
GPIOs used to select the input line.
sound-name-prefix: true

required:
- compatible
- mux-gpios
Expand Down

0 comments on commit 013148f

Please sign in to comment.