devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vakul Garg <vakul@freescale.com>
To: linux-crypto@vger.kernel.org, linuxppc-dev@ozlabs.org,
	devicetree-discuss@lists.ozlabs.org
Subject: [PATCH] Revert "crypto: caam - Updated SEC-4.0 device tree binding for ERA information."
Date: Fri, 7 Dec 2012 14:27:29 +0530	[thread overview]
Message-ID: <1354870649-3656-1-git-send-email-vakul@freescale.com> (raw)

This reverts commit a2c0911c09190125f52c9941b9d187f601c2f7be.

Signed-off-by: Vakul Garg <vakul@freescale.com>
---
Instead of adding SEC era information in crypto node's compatible, a new
property 'fsl,sec-era' is being introduced into crypto node.

 .../devicetree/bindings/crypto/fsl-sec4.txt        |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
index fc9ce6f..bd7ce12 100644
--- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
+++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
@@ -54,8 +54,7 @@ PROPERTIES
    - compatible
       Usage: required
       Value type: <string>
-      Definition: Must include "fsl,sec-v4.0". Also includes SEC
-           ERA versions (optional) with which the device is compatible.
+      Definition: Must include "fsl,sec-v4.0"
 
    - #address-cells
        Usage: required
@@ -107,7 +106,7 @@ PROPERTIES
 
 EXAMPLE
 	crypto@300000 {
-		compatible = "fsl,sec-v4.0", "fsl,sec-era-v2.0";
+		compatible = "fsl,sec-v4.0";
 		#address-cells = <1>;
 		#size-cells = <1>;
 		reg = <0x300000 0x10000>;
-- 
1.7.7.6

             reply	other threads:[~2012-12-07  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  8:57 Vakul Garg [this message]
2012-12-08  4:30 ` [PATCH] Revert "crypto: caam - Updated SEC-4.0 device tree binding for ERA information." Garg Vakul-B16394
2012-12-12 21:29 ` Kumar Gala
2012-12-13  4:04   ` Garg Vakul-B16394

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=1354870649-3656-1-git-send-email-vakul@freescale.com \
    --to=vakul@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-crypto@vger.kernel.org \
    --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).