blob: 9cbf5d9df8fd00d8e2101fd1d3fc22933410a244 [file] [log] [blame]
Andy Grosscca946e2014-03-10 16:40:19 -05001QCOM BAM DMA controller
2
3Required properties:
Archit Tanejace940632014-09-29 10:03:09 +05304- compatible: must be one of the following:
5 * "qcom,bam-v1.4.0" for MSM8974, APQ8074 and APQ8084
6 * "qcom,bam-v1.3.0" for APQ8064, IPQ8064 and MSM8960
Archit Tanejad51da4d2015-02-23 09:40:33 +05307 * "qcom,bam-v1.7.0" for MSM8916
Andy Grosscca946e2014-03-10 16:40:19 -05008- reg: Address range for DMA registers
9- interrupts: Should contain the one interrupt shared by all channels
10- #dma-cells: must be <1>, the cell in the dmas property of the client device
11 represents the channel number
12- clocks: required clock
13- clock-names: must contain "bam_clk" entry
14- qcom,ee : indicates the active Execution Environment identifier (0-7) used in
15 the secure world.
Stanimir Varbanovc778ed42016-04-11 11:38:40 +030016- qcom,controlled-remotely : optional, indicates that the bam is controlled by
17 remote proccessor i.e. execution environment.
Andy Grosscca946e2014-03-10 16:40:19 -050018
19Example:
20
21 uart-bam: dma@f9984000 = {
22 compatible = "qcom,bam-v1.4.0";
23 reg = <0xf9984000 0x15000>;
24 interrupts = <0 94 0>;
25 clocks = <&gcc GCC_BAM_DMA_AHB_CLK>;
26 clock-names = "bam_clk";
27 #dma-cells = <1>;
28 qcom,ee = <0>;
29 };
30
31DMA clients must use the format described in the dma.txt file, using a two cell
32specifier for each channel.
33
34Example:
35 serial@f991e000 {
36 compatible = "qcom,msm-uart";
37 reg = <0xf991e000 0x1000>
38 <0xf9944000 0x19000>;
39 interrupts = <0 108 0>;
40 clocks = <&gcc GCC_BLSP1_UART2_APPS_CLK>,
41 <&gcc GCC_BLSP1_AHB_CLK>;
42 clock-names = "core", "iface";
43
44 dmas = <&uart-bam 0>, <&uart-bam 1>;
45 dma-names = "rx", "tx";
46 };