linux-kernel - [PATCH] devicetree: add ibm-nx-powernv details

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed,  8 Apr 2015 23:05:56 -0400
From:	Dan Streetman <ddstreet@...e.org>
To:	Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Michael Ellerman <mpe@...erman.id.au>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>
Cc:	linuxppc-dev@...ts.ozlabs.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, Dan Streetman <ddstreet@...e.org>
Subject: [PATCH] devicetree: add ibm-nx-powernv details

Add a devicetree description for property nodes for the NX Coprocessor
in an IBM PowerPC processor.

Signed-off-by: Dan Streetman <ddstreet@...e.org>
---

Is this the right location/naming for this file?
And did I get the content format right?

Should this file be called "ibm-nx-opal.txt" instead of "ibm-nx-powernv.txt",
since it's the Opal firmware that provides the nodes (although they are
used by the PowerNV platform kernel)?

The 842 properties are used by the PowerNV 842 driver patch set I
sent out yesterday, and which I'll send a v2 of soon.

.../devicetree/bindings/crypto/ibm-nx-powernv.txt  | 40 ++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/crypto/ibm-nx-powernv.txt

diff --git a/Documentation/devicetree/bindings/crypto/ibm-nx-powernv.txt b/Documentation/devicetree/bindings/crypto/ibm-nx-powernv.txt
new file mode 100644
index 0000000..e031636
--- /dev/null
+++ b/Documentation/devicetree/bindings/crypto/ibm-nx-powernv.txt
@@ -0,0 +1,40 @@
+Device-tree bindings for PowerNV platform IBM Nest (NX) Coprocessor
+-------------------------------------------------------------------
+
+Required properties:
+
+- compatible: must contain "ibm,power-nx"; may also contain the processor
+              version, e.g. "ibm,power8-nx"
+
+Optional properties:
+
+- ibm,842-coprocessor-type: CT of this NX 842 coprocessor
+- ibm,842-coprocessor-instance: CI of this NX 842 coprocessor
+
+If present, the NX-842 Coprocessor Type (CT) and Coprocessor Instance (CI)
+can be used in an ICSWX instruction to communicate with the NX-842
+coprocessor, to perform hardware compression/decompression.
+
+Additionally, there must be an "ibm,chip-id" node at some point in the
+direct devicetree hierarchy leading to the nx node; typically the nx
+node's parent is an xscom node, which contains the "ibm,chip-id" property.
+
+Example:
+
+nx@...0000 {
+	compatible = "ibm,power-nx", "ibm,power8-nx";
+	ibm,842-coprocessor-type = <0x3>;
+	ibm,842-coprocessor-instance = <0x1>;
+	name = "nx";
+	reg = <0x2010000 0x4000>;
+	linux,phandle = <0x85>;
+	phandle = <0x85>;
+};
+
+with a parent of:
+
+xscom@...0000000000 {
+	ibm,chip-id = <0x0>;
+	nx@...0000;
+	...
+};
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/