aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Branden2015-03-20 20:06:22 -0500
committerRob Herring2015-03-26 12:14:11 -0500
commit23a71fd616bf77fcc630ea514c469b0dd09cb99c (patch)
tree9172aa58dea51022af10f8f910dbdf00c120511c /Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt
parent9697a5595ece52a722d88f25a90ded0028e5e6b4 (diff)
downloadti-linux-kernel-23a71fd616bf77fcc630ea514c469b0dd09cb99c.tar.gz
ti-linux-kernel-23a71fd616bf77fcc630ea514c469b0dd09cb99c.tar.xz
ti-linux-kernel-23a71fd616bf77fcc630ea514c469b0dd09cb99c.zip
dt-bindings: brcm: rationalize Broadcom documentation naming
This patchset attempts to standardize the naming of dt-bindings documents based on the Broadcom vendor prefix of brcm. Although there are no guidelines currently present for how to name the dt-bindings document the "vendor,binding.txt" style is in use by some of the other vendors. Acked-by: Lee Jones <lee@kernel.org> Acked-by: Florian Fainelli <f.fainelli@gmail.com> Acked-by: Gregory Fong <gregory.0xf0@gmail.com> Acked-by: Stephen Warren <swarren@wwwdotorg.org> Signed-off-by: Scott Branden <sbranden@broadcom.com> Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt')
-rw-r--r--Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt25
1 files changed, 25 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt b/Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt
new file mode 100644
index 000000000000..65783de0aedf
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt
@@ -0,0 +1,25 @@
1* Broadcom BCM2835 SoC I2S/PCM module
2
3Required properties:
4- compatible: "brcm,bcm2835-i2s"
5- reg: A list of base address and size entries:
6 * The first entry should cover the PCM registers
7 * The second entry should cover the PCM clock registers
8- dmas: List of DMA controller phandle and DMA request line ordered pairs.
9- dma-names: Identifier string for each DMA request line in the dmas property.
10 These strings correspond 1:1 with the ordered pairs in dmas.
11
12 One of the DMA channels will be responsible for transmission (should be
13 named "tx") and one for reception (should be named "rx").
14
15Example:
16
17bcm2835_i2s: i2s@7e203000 {
18 compatible = "brcm,bcm2835-i2s";
19 reg = <0x7e203000 0x20>,
20 <0x7e101098 0x02>;
21
22 dmas = <&dma 2>,
23 <&dma 3>;
24 dma-names = "tx", "rx";
25};