ASoC: dt-bindings: Convert brcm,bcm2835-i2s to DT schema
Subsystems (5)
Rob Herring (Arm)
maintainerPATCH 1/1 ASoC: dt-bindings: Convert brcm,bcm2835-i2s to DT schema
Convert the Broadcom BCM2835 I2S/PCM binding to DT schema format. It's a straightforward conversion.
--- .../bindings/sound/brcm,bcm2835-i2s.txt | 24 --------- .../bindings/sound/brcm,bcm2835-i2s.yaml | 51 +++++++++++++++++++ 2 files changed, 51 insertions(+), 24 deletions(-) delete mode 100644 Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.yaml
Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt deleted +0 -24
@@ -1,24 +0,0 @@ -* Broadcom BCM2835 SoC I2S/PCM module - -Required properties: -- compatible: "brcm,bcm2835-i2s" -- reg: Should contain PCM registers location and length. -- clocks: the (PCM) clock to use -- dmas: List of DMA controller phandle and DMA request line ordered pairs. -- dma-names: Identifier string for each DMA request line in the dmas property. - These strings correspond 1:1 with the ordered pairs in dmas. - - One of the DMA channels will be responsible for transmission (should be - named "tx") and one for reception (should be named "rx"). - -Example: - -bcm2835_i2s: i2s@7e203000 { - compatible = "brcm,bcm2835-i2s"; - reg = <0x7e203000 0x24>; - clocks = <&clocks BCM2835_CLOCK_PCM>; - - dmas = <&dma 2>, - <&dma 3>; - dma-names = "tx", "rx"; -};
Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.yaml new file +51 -0
51 lines not on this page · raw message
Signature · 1 line
2.47.2
Mark Brown
maintainerQuoted 4 lines · Rob Herring (Arm)
Convert the Broadcom BCM2835 I2S/PCM binding to DT schema format. It's a straightforward conversion.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: Convert brcm,bcm2835-i2s to DT schema
commit: bab4ab484a6ca170847da9bffe86f1fa90df4bbe
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