diff options
| -rw-r--r-- | Documentation/devicetree/bindings/dma/arm,pl330.yaml | 83 | ||||
| -rw-r--r-- | Documentation/devicetree/bindings/dma/arm-pl330.txt | 49 | 
2 files changed, 83 insertions, 49 deletions
| diff --git a/Documentation/devicetree/bindings/dma/arm,pl330.yaml b/Documentation/devicetree/bindings/dma/arm,pl330.yaml new file mode 100644 index 000000000000..decab185cf4d --- /dev/null +++ b/Documentation/devicetree/bindings/dma/arm,pl330.yaml @@ -0,0 +1,83 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/dma/arm,pl330.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: ARM PrimeCell PL330 DMA Controller + +maintainers: +  - Vinod Koul <vkoul@kernel.org> + +description: +  The ARM PrimeCell PL330 DMA controller can move blocks of memory contents +  between memory and peripherals or memory to memory. + +# We need a select here so we don't match all nodes with 'arm,primecell' +select: +  properties: +    compatible: +      contains: +        const: arm,pl330 +  required: +    - compatible + +allOf: +  - $ref: dma-controller.yaml# +  - $ref: /schemas/arm/primecell.yaml# + +properties: +  compatible: +    items: +      - enum: +          - arm,pl330 +      - const: arm,primecell + +  reg: +    maxItems: 1 + +  interrupts: +    minItems: 1 +    maxItems: 32 +    description: A single combined interrupt or an interrupt per event + +  '#dma-cells': +    const: 1 +    description: Contains the DMA request number for the consumer + +  arm,pl330-broken-no-flushp: +    type: boolean +    description: quirk for avoiding to execute DMAFLUSHP + +  arm,pl330-periph-burst: +    type: boolean +    description: quirk for performing burst transfer only + +  dma-coherent: true + +  resets: +    minItems: 1 +    maxItems: 2 + +  reset-names: +    minItems: 1 +    items: +      - const: dma +      - const: dma-ocp + +required: +  - compatible +  - reg +  - interrupts + +unevaluatedProperties: false + +examples: +  - | +    dma-controller@12680000 { +        compatible = "arm,pl330", "arm,primecell"; +        reg = <0x12680000 0x1000>; +        interrupts = <99>; +        #dma-cells = <1>; +    }; +... diff --git a/Documentation/devicetree/bindings/dma/arm-pl330.txt b/Documentation/devicetree/bindings/dma/arm-pl330.txt deleted file mode 100644 index 315e90122afa..000000000000 --- a/Documentation/devicetree/bindings/dma/arm-pl330.txt +++ /dev/null @@ -1,49 +0,0 @@ -* ARM PrimeCell PL330 DMA Controller - -The ARM PrimeCell PL330 DMA controller can move blocks of memory contents -between memory and peripherals or memory to memory. - -Required properties: -  - compatible: should include both "arm,pl330" and "arm,primecell". -  - reg: physical base address of the controller and length of memory mapped -    region. -  - interrupts: interrupt number to the cpu. - -Optional properties: -  - dma-coherent      : Present if dma operations are coherent -  - #dma-cells: must be <1>. used to represent the number of integer -    cells in the dmas property of client device. -  - dma-channels: contains the total number of DMA channels supported by the DMAC -  - dma-requests: contains the total number of DMA requests supported by the DMAC -  - arm,pl330-broken-no-flushp: quirk for avoiding to execute DMAFLUSHP -  - arm,pl330-periph-burst: quirk for performing burst transfer only -  - resets: contains an entry for each entry in reset-names. -	    See ../reset/reset.txt for details. -  - reset-names: must contain at least "dma", and optional is "dma-ocp". - -Example: - -	pdma0: pdma@12680000 { -		compatible = "arm,pl330", "arm,primecell"; -		reg = <0x12680000 0x1000>; -		interrupts = <99>; -		#dma-cells = <1>; -		#dma-channels = <8>; -		#dma-requests = <32>; -	}; - -Client drivers (device nodes requiring dma transfers from dev-to-mem or -mem-to-dev) should specify the DMA channel numbers and dma channel names -as shown below. - -  [property name]  = <[phandle of the dma controller] [dma request id]>; -  [property name]  = <[dma channel name]> - -      where 'dma request id' is the dma request number which is connected -      to the client controller. The 'property name' 'dmas' and 'dma-names' -      as required by the generic dma device tree binding helpers. The dma -      names correspond 1:1 with the dma request ids in the dmas property. - -  Example:  dmas = <&pdma0 12 -		    &pdma1 11>; -	    dma-names = "tx", "rx"; | 
