Skip to contentSkip to conversation

ASoC: dt-bindings: audio-graph-port: Drop type from "clocks"

PATCH In review Rob Herring 2 participants 2 messages Jan 24, 2024 – Jan 26, 2024

Subsystems (4)
lore
Share & tools
lore

Rob Herring

author maintainer
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: audio-graph-port: Drop type from "clocks"

"clocks" is a standard property which already has a type. Users only need to define how many clocks and what each clock is if more than 1 clock.

---
 Documentation/devicetree/bindings/sound/audio-graph-port.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/sound/audio-graph-port.yaml +1 -1
index b13c08de505e..28b27e7e45de 100644
@@ -51,7 +51,7 @@ definitions:
           - $ref: /schemas/types.yaml#/definitions/phandle
       clocks:
         description: Indicates system clock
-        $ref: /schemas/types.yaml#/definitions/phandle
+        maxItems: 1
       system-clock-frequency:
         $ref: simple-card.yaml#/definitions/system-clock-frequency
       system-clock-direction-out:
Signature · 1 line
2.43.0
maintainer
#1 lore raw
Quoted 4 lines · Rob Herring

"clocks" is a standard property which already has a type. Users only need to define how many clocks and what each clock is if more than 1 clock.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: dt-bindings: audio-graph-port: Drop type from "clocks"

      commit: 01dffdcaa094858a03e3694694815f1a4915940c

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