Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932317AbbDIDG0 (ORCPT ); Wed, 8 Apr 2015 23:06:26 -0400 Received: from mail-ig0-f175.google.com ([209.85.213.175]:37132 "EHLO mail-ig0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754608AbbDIDGX (ORCPT ); Wed, 8 Apr 2015 23:06:23 -0400 From: Dan Streetman To: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Herbert Xu , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras Cc: linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Dan Streetman Subject: [PATCH] devicetree: add ibm-nx-powernv details Date: Wed, 8 Apr 2015 23:05:56 -0400 Message-Id: <1428548756-16485-1-git-send-email-ddstreet@ieee.org> X-Mailer: git-send-email 2.1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2478 Lines: 74 Add a devicetree description for property nodes for the NX Coprocessor in an IBM PowerPC processor. Signed-off-by: Dan Streetman --- 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@2010000 { + 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@3fc0000000000 { + ibm,chip-id = <0x0>; + nx@2010000; + ... +}; -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/