mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-04 16:15:11 +00:00
4da722ca19
Pretty much any node can have a status property, so it doesn't need to be in examples. Converted with the following command and removed examples with SoC and board specific splits: git grep -l -E 'status.*=.*' Documentation/devicetree/ | xargs sed -i -E '/\sstatus.*=.*"(disabled|ok|okay)/d' Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Rob Herring <robh@kernel.org>
40 lines
1.2 KiB
Text
40 lines
1.2 KiB
Text
* Marvell XOR engines
|
|
|
|
Required properties:
|
|
- compatible: Should be one of the following:
|
|
- "marvell,orion-xor"
|
|
- "marvell,armada-380-xor"
|
|
- "marvell,armada-3700-xor".
|
|
- reg: Should contain registers location and length (two sets)
|
|
the first set is the low registers, the second set the high
|
|
registers for the XOR engine.
|
|
- clocks: pointer to the reference clock
|
|
|
|
The DT node must also contains sub-nodes for each XOR channel that the
|
|
XOR engine has. Those sub-nodes have the following required
|
|
properties:
|
|
- interrupts: interrupt of the XOR channel
|
|
|
|
The sub-nodes used to contain one or several of the following
|
|
properties, but they are now deprecated:
|
|
- dmacap,memcpy to indicate that the XOR channel is capable of memcpy operations
|
|
- dmacap,memset to indicate that the XOR channel is capable of memset operations
|
|
- dmacap,xor to indicate that the XOR channel is capable of xor operations
|
|
- dmacap,interrupt to indicate that the XOR channel is capable of
|
|
generating interrupts
|
|
|
|
Example:
|
|
|
|
xor@d0060900 {
|
|
compatible = "marvell,orion-xor";
|
|
reg = <0xd0060900 0x100
|
|
0xd0060b00 0x100>;
|
|
clocks = <&coreclk 0>;
|
|
|
|
xor00 {
|
|
interrupts = <51>;
|
|
};
|
|
xor01 {
|
|
interrupts = <52>;
|
|
};
|
|
};
|