Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit bfda74ad authored by Antoine Tenart's avatar Antoine Tenart Committed by Herbert Xu
Browse files

Documentation/bindings: crypto: inside-secure: update the compatibles 



The compatibles were updated in the Inside Secure SafeXcel cryptographic
driver, as the ones previously used were not specific enough. The old
compatibles are still supported by the driver for backward
compatibility.

This patch updates the documentation accordingly.

Signed-off-by: default avatarAntoine Tenart <antoine.tenart@bootlin.com>
Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
parent 7d8f52a3

Documentation/devicetree/bindings/crypto/inside-secure-safexcel.txt

+11 −3
Original line number Diff line number Diff line 
Inside Secure SafeXcel cryptographic engine



Required properties:

- compatible: Should be "inside-secure,safexcel-eip197" or

              "inside-secure,safexcel-eip97".

- compatible: Should be "inside-secure,safexcel-eip197b" or

              "inside-secure,safexcel-eip97ies".

- reg: Base physical address of the engine and length of memory mapped region.

- interrupts: Interrupt numbers for the rings and engine.

- interrupt-names: Should be "ring0", "ring1", "ring2", "ring3", "eip", "mem".
@@ -14,10 +14,18 @@ Optional properties: 
               name must be "core" for the first clock and "reg" for

               the second one.



Backward compatibility:

Two compatibles are kept for backward compatibility, but shouldn't be used for

new submissions:

- "inside-secure,safexcel-eip197" is equivalent to

  "inside-secure,safexcel-eip197b".

- "inside-secure,safexcel-eip97" is equivalent to

  "inside-secure,safexcel-eip97ies".



Example:



	crypto: crypto@800000 {

		compatible = "inside-secure,safexcel-eip197";

		compatible = "inside-secure,safexcel-eip197b";

		reg = <0x800000 0x200000>;

		interrupts = <GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>,

			     <GIC_SPI 54 IRQ_TYPE_LEVEL_HIGH>,