Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

dt-bindings: dma: pl330: Convert to DT schema

Convert the Arm PL330 DMA controller binding to DT schema.

The '#dma-channels' and '#dma-requests' properties are unused as they are
discoverable and are non-standard (the standard props don't have '#'). So
drop them from the binding.

Cc: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20211217170644.3145332-1-robh@kernel.org
Signed-off-by: Vinod Koul <vkoul@kernel.org>

authored by

Rob Herring and committed by
Vinod Koul
29f30634 e7f11088

+83 -49
+83
Documentation/devicetree/bindings/dma/arm,pl330.yaml
··· 1 + # SPDX-License-Identifier: GPL-2.0 2 + %YAML 1.2 3 + --- 4 + $id: http://devicetree.org/schemas/dma/arm,pl330.yaml# 5 + $schema: http://devicetree.org/meta-schemas/core.yaml# 6 + 7 + title: ARM PrimeCell PL330 DMA Controller 8 + 9 + maintainers: 10 + - Vinod Koul <vkoul@kernel.org> 11 + 12 + description: 13 + The ARM PrimeCell PL330 DMA controller can move blocks of memory contents 14 + between memory and peripherals or memory to memory. 15 + 16 + # We need a select here so we don't match all nodes with 'arm,primecell' 17 + select: 18 + properties: 19 + compatible: 20 + contains: 21 + const: arm,pl330 22 + required: 23 + - compatible 24 + 25 + allOf: 26 + - $ref: dma-controller.yaml# 27 + - $ref: /schemas/arm/primecell.yaml# 28 + 29 + properties: 30 + compatible: 31 + items: 32 + - enum: 33 + - arm,pl330 34 + - const: arm,primecell 35 + 36 + reg: 37 + maxItems: 1 38 + 39 + interrupts: 40 + minItems: 1 41 + maxItems: 32 42 + description: A single combined interrupt or an interrupt per event 43 + 44 + '#dma-cells': 45 + const: 1 46 + description: Contains the DMA request number for the consumer 47 + 48 + arm,pl330-broken-no-flushp: 49 + type: boolean 50 + description: quirk for avoiding to execute DMAFLUSHP 51 + 52 + arm,pl330-periph-burst: 53 + type: boolean 54 + description: quirk for performing burst transfer only 55 + 56 + dma-coherent: true 57 + 58 + resets: 59 + minItems: 1 60 + maxItems: 2 61 + 62 + reset-names: 63 + minItems: 1 64 + items: 65 + - const: dma 66 + - const: dma-ocp 67 + 68 + required: 69 + - compatible 70 + - reg 71 + - interrupts 72 + 73 + unevaluatedProperties: false 74 + 75 + examples: 76 + - | 77 + dma-controller@12680000 { 78 + compatible = "arm,pl330", "arm,primecell"; 79 + reg = <0x12680000 0x1000>; 80 + interrupts = <99>; 81 + #dma-cells = <1>; 82 + }; 83 + ...
-49
Documentation/devicetree/bindings/dma/arm-pl330.txt
··· 1 - * ARM PrimeCell PL330 DMA Controller 2 - 3 - The ARM PrimeCell PL330 DMA controller can move blocks of memory contents 4 - between memory and peripherals or memory to memory. 5 - 6 - Required properties: 7 - - compatible: should include both "arm,pl330" and "arm,primecell". 8 - - reg: physical base address of the controller and length of memory mapped 9 - region. 10 - - interrupts: interrupt number to the cpu. 11 - 12 - Optional properties: 13 - - dma-coherent : Present if dma operations are coherent 14 - - #dma-cells: must be <1>. used to represent the number of integer 15 - cells in the dmas property of client device. 16 - - dma-channels: contains the total number of DMA channels supported by the DMAC 17 - - dma-requests: contains the total number of DMA requests supported by the DMAC 18 - - arm,pl330-broken-no-flushp: quirk for avoiding to execute DMAFLUSHP 19 - - arm,pl330-periph-burst: quirk for performing burst transfer only 20 - - resets: contains an entry for each entry in reset-names. 21 - See ../reset/reset.txt for details. 22 - - reset-names: must contain at least "dma", and optional is "dma-ocp". 23 - 24 - Example: 25 - 26 - pdma0: pdma@12680000 { 27 - compatible = "arm,pl330", "arm,primecell"; 28 - reg = <0x12680000 0x1000>; 29 - interrupts = <99>; 30 - #dma-cells = <1>; 31 - #dma-channels = <8>; 32 - #dma-requests = <32>; 33 - }; 34 - 35 - Client drivers (device nodes requiring dma transfers from dev-to-mem or 36 - mem-to-dev) should specify the DMA channel numbers and dma channel names 37 - as shown below. 38 - 39 - [property name] = <[phandle of the dma controller] [dma request id]>; 40 - [property name] = <[dma channel name]> 41 - 42 - where 'dma request id' is the dma request number which is connected 43 - to the client controller. The 'property name' 'dmas' and 'dma-names' 44 - as required by the generic dma device tree binding helpers. The dma 45 - names correspond 1:1 with the dma request ids in the dmas property. 46 - 47 - Example: dmas = <&pdma0 12 48 - &pdma1 11>; 49 - dma-names = "tx", "rx";