The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition)


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/contrib/device-tree/Bindings/dma/qcom_bam_dma.txt

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

    1 QCOM BAM DMA controller
    2 
    3 Required properties:
    4 - 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
    7  * "qcom,bam-v1.7.0" for MSM8916
    8 - 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.
   16 - qcom,controlled-remotely : optional, indicates that the bam is controlled by
   17   remote proccessor i.e. execution environment.
   18 - qcom,powered-remotely : optional, indicates that the bam is powered up by
   19   a remote processor but must be initialized by the local processor.
   20 - num-channels : optional, indicates supported number of DMA channels in a
   21   remotely controlled bam.
   22 - qcom,num-ees : optional, indicates supported number of Execution Environments
   23   in a remotely controlled bam.
   24 
   25 Example:
   26 
   27         uart-bam: dma@f9984000 = {
   28                 compatible = "qcom,bam-v1.4.0";
   29                 reg = <0xf9984000 0x15000>;
   30                 interrupts = <0 94 0>;
   31                 clocks = <&gcc GCC_BAM_DMA_AHB_CLK>;
   32                 clock-names = "bam_clk";
   33                 #dma-cells = <1>;
   34                 qcom,ee = <0>;
   35         };
   36 
   37 DMA clients must use the format described in the dma.txt file, using a two cell
   38 specifier for each channel.
   39 
   40 Example:
   41         serial@f991e000 {
   42                 compatible = "qcom,msm-uart";
   43                 reg = <0xf991e000 0x1000>
   44                         <0xf9944000 0x19000>;
   45                 interrupts = <0 108 0>;
   46                 clocks = <&gcc GCC_BLSP1_UART2_APPS_CLK>,
   47                         <&gcc GCC_BLSP1_AHB_CLK>;
   48                 clock-names = "core", "iface";
   49 
   50                 dmas = <&uart-bam 0>, <&uart-bam 1>;
   51                 dma-names = "rx", "tx";
   52         };

Cache object: 16a4a2bcf4a094b0dfc7991a3ba151de


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.