mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
synced 2026-04-20 04:23:55 -04:00
791d3ef2e1
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
27 lines
872 B
Plaintext
27 lines
872 B
Plaintext
Xilinx ZynqMP DMA engine, it does support memory to memory transfers,
|
|
memory to device and device to memory transfers. It also has flow
|
|
control and rate control support for slave/peripheral dma access.
|
|
|
|
Required properties:
|
|
- compatible : Should be "xlnx,zynqmp-dma-1.0"
|
|
- reg : Memory map for gdma/adma module access.
|
|
- interrupts : Should contain DMA channel interrupt.
|
|
- xlnx,bus-width : Axi buswidth in bits. Should contain 128 or 64
|
|
- clock-names : List of input clocks "clk_main", "clk_apb"
|
|
(see clock bindings for details)
|
|
|
|
Optional properties:
|
|
- dma-coherent : Present if dma operations are coherent.
|
|
|
|
Example:
|
|
++++++++
|
|
fpd_dma_chan1: dma@fd500000 {
|
|
compatible = "xlnx,zynqmp-dma-1.0";
|
|
reg = <0x0 0xFD500000 0x1000>;
|
|
interrupt-parent = <&gic>;
|
|
interrupts = <0 117 4>;
|
|
clock-names = "clk_main", "clk_apb";
|
|
xlnx,bus-width = <128>;
|
|
dma-coherent;
|
|
};
|