[PATCH] ASoC: dt-bindings: rt5682s: fix the device-tree schema errors
From: Derek Fang derek.fang@realtek.com
Fix the device-tree schema errors that be reported by using 'make dt_binding_check'.
Signed-off-by: Derek Fang derek.fang@realtek.com --- .../devicetree/bindings/sound/realtek,rt5682s.yaml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml b/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml index 7a5f1d0fd3e2..2b8b7b51fe55 100644 --- a/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml +++ b/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml @@ -29,6 +29,8 @@ properties: - 0 # dmic1 data is not used - 1 # using GPIO2 pin as dmic1 data pin - 2 # using GPIO5 pin as dmic1 data pin + description: | + Specify which GPIO pin be used as DMIC1 data pin.
realtek,dmic1-clk-pin: $ref: /schemas/types.yaml#/definitions/uint32 @@ -36,12 +38,16 @@ properties: - 0 # dmic1 clk is not used - 1 # using GPIO1 pin as dmic1 clock pin - 2 # using GPIO3 pin as dmic1 clock pin + description: | + Specify which GPIO pin be used as DMIC1 clk pin.
realtek,jd-src: $ref: /schemas/types.yaml#/definitions/uint32 enum: - 0 # No JD is used - 1 # using JD1 as JD source + description: | + Specify which JD source be used.
realtek,ldo1-en-gpios: description: | @@ -72,9 +78,9 @@ properties: const: 1
clock-output-names: - items: - - description: Name given for DAI word clock output. - - description: Name given for DAI bit clock output. + minItems: 2 + maxItems: 2 + description: Name given for DAI word clock and bit clock outputs.
additionalProperties: false
On Wed, 29 Sep 2021 21:04:06 +0800, derek.fang@realtek.com wrote:
From: Derek Fang derek.fang@realtek.com
Fix the device-tree schema errors that be reported by using 'make dt_binding_check'.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: rt5682s: fix the device-tree schema errors commit: 91cf45595021bd6f6279748aa472de7fc7864084
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
participants (2)
-
derek.fang@realtek.com
-
Mark Brown