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
702 B
Plaintext
22 lines
702 B
Plaintext
Picochip picoXcell SPAcc (Security Protocol Accelerator) bindings
|
|
|
|
Picochip picoXcell devices contain crypto offload engines that may be used for
|
|
IPSEC and femtocell layer 2 ciphering.
|
|
|
|
Required properties:
|
|
- compatible : "picochip,spacc-ipsec" for the IPSEC offload engine
|
|
"picochip,spacc-l2" for the femtocell layer 2 ciphering engine.
|
|
- reg : Offset and length of the register set for this device
|
|
- interrupts : The interrupt line from the SPAcc.
|
|
- ref-clock : The input clock that drives the SPAcc.
|
|
|
|
Example SPAcc node:
|
|
|
|
spacc@10000 {
|
|
compatible = "picochip,spacc-ipsec";
|
|
reg = <0x100000 0x10000>;
|
|
interrupt-parent = <&vic0>;
|
|
interrupts = <24>;
|
|
ref-clock = <&ipsec_clk>, "ref";
|
|
};
|