mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07: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>
22 lines
676 B
Plaintext
22 lines
676 B
Plaintext
Arm TrustZone CryptoCell cryptographic engine
|
|
|
|
Required properties:
|
|
- compatible: Should be one of: "arm,cryptocell-712-ree",
|
|
"arm,cryptocell-710-ree" or "arm,cryptocell-630p-ree".
|
|
- reg: Base physical address of the engine and length of memory mapped region.
|
|
- interrupts: Interrupt number for the device.
|
|
|
|
Optional properties:
|
|
- clocks: Reference to the crypto engine clock.
|
|
- dma-coherent: Present if dma operations are coherent.
|
|
|
|
Examples:
|
|
|
|
arm_cc712: crypto@80000000 {
|
|
compatible = "arm,cryptocell-712-ree";
|
|
interrupt-parent = <&intc>;
|
|
interrupts = < 0 30 4 >;
|
|
reg = < 0x80000000 0x10000 >;
|
|
|
|
};
|