linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH] powerpc: Add FSL SEC node to documentation
Date: Mon, 20 Mar 2006 19:59:45 -0600	[thread overview]
Message-ID: <20060320195945.004fdf26.kim.phillips@freescale.com> (raw)

Documentation: Added FSL SOC SEC node definition

Updated the documentation to include the definition of the SEC device
node format for Freescale SOC devices.

Signed-off-by: Kim Phillips <kim.phillips@freescale.com>

---
commit 97d971c1d30e77a453cacaef72c32e00381ab02a
tree 4b815caece1c05b33309f8852eeccd90f020ca49
parent c4a1745aa09fc110afdefea0e5d025043e348bae
author Kim Phillips <kim.phillips@freescale.com> Mon, 20 Mar 2006 19:31:21 -0600
committer Kim Phillips <kim.phillips@freescale.com> Mon, 20 Mar 2006 19:31:21 -0600

 Documentation/powerpc/booting-without-of.txt |   73 ++++++++++++++++++++++++++
 1 files changed, 73 insertions(+), 0 deletions(-)

diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index d02c649..72f3241 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -1365,6 +1365,79 @@ platforms are moved over to use the flat
 	};
 
 
+   g) Freescale SOC SEC Security Engines
+
+   Required properties:
+
+    - device_type : Should be "crypto"
+    - model : Model of the device.  Should be "SEC1" or "SEC2"
+    - compatible : Should be "talitos"
+    - reg : Offset and length of the register set for the device
+    - interrupts : <a b> where a is the interrupt number and b is a
+      field that represents an encoding of the sense and level
+      information for the interrupt.  This should be encoded based on
+      the information in section 2) depending on the type of interrupt
+      controller you have.
+    - interrupt-parent : the phandle for the interrupt controller that
+      services interrupts for this device.
+    - num-channels : An integer representing the number of channels
+      available.  Most modern SEC's have 4 channels.
+    - channel-fifo-len : An integer representing the number of descriptor
+      pointers each channel fetch fifo can hold.  Most modern SEC channel 
+      fetch fifos can hold 24 descriptor pointers.
+    - exec-units-mask : The bitmask representing what execution units (EUs)
+      are available. It's a single 32 bit cell. EU information should be
+      encoded following the SEC's Descriptor Header Dword EU_SEL0 field 
+      documentation, i.e. as follows:
+
+        bit 0 = reserved - should be 0
+        bit 1 = set if SEC has the ARC4 EU (AFEU)
+        bit 2 = set if SEC has the DES/3DES EU (DEU)
+        bit 3 = set if SEC has the message digest EU (MDEU)
+        bit 4 = set if SEC has the random number generator EU (RNG)
+        bit 5 = set if SEC has the public key EU (PKEU)
+        bit 6 = set if SEC has the AES EU (AESU)
+        bit 7 = set if SEC has the Kasumi EU (KEU)
+
+      bits 8 through 31 are reserved for future SEC EUs.
+
+    - descriptor-types-mask : The bitmask representing what descriptors
+      are available. It's a single 32 bit cell. Descriptor type information 
+      should be encoded as follows:
+
+        bit 0  = set if SEC supports the aesu_ctr_nonsnoop descriptor type
+        bit 1  = set if SEC supports the ipsec_esp descriptor type
+        bit 2  = set if SEC supports the common_nonsnoop descriptor type
+        bit 3  = set if SEC supports the 802.11i AES ccmp descriptor type
+        bit 4  = set if SEC supports the hmac_snoop_no_afeu descriptor type
+        bit 5  = set if SEC supports the srtp descriptor type
+        bit 6  = reserved - should be 0
+        bit 7  = set if SEC supports the pkeu_assemble descriptor type
+        bit 8  = reserved - should be 0
+        bit 9  = set if SEC supports the pkeu_ptmul descriptor type
+        bit 10 = set if SEC supports the common_nonsnoop_afeu descriptor type
+        bit 11 = set if SEC supports the pkeu_ptadd_dbl descriptor type
+
+      ..and so on and so forth, following the SEC's Descriptor Header Dword
+      DESC_TYPE field definition in reference documentation.
+ 
+  Example:
+
+	/* MPC8548E */
+	crypto@30000 {
+		device_type = "crypto";
+		model = "SEC2";
+		compatible = "talitos";
+		reg = <30000 10000>;
+		interrupts = <1d 3>;
+		interrupt-parent = <40000>;
+		num-channels = <4>;
+		channel-fifo-len = <24>;
+		exec-units-mask = <000000fe>;
+		descriptor-types-mask = <073f1127>;
+	};
+
+
    More devices will be defined as this spec matures.
 
 

-- 

             reply	other threads:[~2006-03-21  2:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21  1:59 Kim Phillips [this message]
2006-03-21  2:14 ` [PATCH] powerpc: Add FSL SEC node to documentation Hollis Blanchard
2006-03-21 17:48   ` Kim Phillips
2006-03-21 18:21     ` Kumar Gala
2006-03-22  1:10       ` Kim Phillips
2006-03-22  4:09         ` Paul Mackerras
2006-03-21 18:25   ` Kumar Gala
2006-03-21 19:28     ` Hollis Blanchard
2006-03-21 21:23       ` Paul Nasrat
2006-03-25 22:27         ` Doug Maxey
  -- strict thread matches above, loose matches on Subject: below --
2006-03-22 20:39 Kim Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060320195945.004fdf26.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).