diff options
| author | Dan Streetman <ddstreet@ieee.org> | 2015-03-17 12:31:50 -0400 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-03-19 02:50:40 +1100 |
| commit | d2e2c797f95900513eeb4ab5b5f7e0b42753c41e (patch) | |
| tree | 4a3051edd67f37325007ff6cf956d20524904ab6 /doc | |
| parent | 672f26aeae18352e1fe8e4c7030cf1e338188487 (diff) | |
| download | skiboot-d2e2c797f95900513eeb4ab5b5f7e0b42753c41e.zip skiboot-d2e2c797f95900513eeb4ab5b5f7e0b42753c41e.tar.gz skiboot-d2e2c797f95900513eeb4ab5b5f7e0b42753c41e.tar.bz2 | |
update device tree doc for NX node location
I think the device tree doc update for the new NX node location
got lost from the last patch; this updates the nx device node doc
with the right information.
Signed-off-by: Dan Streetman <ddstreet@ieee.org>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/device-tree/nx.txt | 42 |
1 files changed, 20 insertions, 22 deletions
diff --git a/doc/device-tree/nx.txt b/doc/device-tree/nx.txt index 6c48956..84c97ac 100644 --- a/doc/device-tree/nx.txt +++ b/doc/device-tree/nx.txt @@ -8,9 +8,25 @@ xscom node, as: /xscom@<xscom_addr>/nx@<nx_addr> With unique xscom and nx addresses. Their compatible node contains -"ibm,power-nx". There is nothing that the OS should directly do with the -NX nodes, instead the specific coprocessor nodes should be used, as -described below. +"ibm,power-nx". + + +NX 842 Coprocessor +------------------ + +This is the memory compression coprocessor, which uses the IBM proprietary +842 compression algorithm and format. Each nx node contains an 842 engine. + +ibm,842-coprocessor-type : CT value common to all 842 coprocessors +ibm,842-coprocessor-instance : CI value unique to all 842 coprocessors + +Access to the coprocessor requires using the ICSWX instruction, which uses +a specific format including a Coprocessor Type (CT) and Coprocessor Instance +(CI) value to address each request to the right coprocessor. The driver should +use the CT and CI values for a particular node to communicate with it. For +all 842 coprocessors in the system, the CT value will (should) be the same, +while each will have a different CI value. The driver can use CI 0 to allow +the hardware to automatically select which coprocessor instance to use. NX RNG Coprocessor @@ -18,7 +34,7 @@ NX RNG Coprocessor This is the Random Number Generator (RNG) coprocessor, which is a part of each NX coprocessor. Each node represents a unique RNG coprocessor. -The nodes are located at: +Its nodes are not under the main nx node, they are located at: /hwrng@<addr> : RNG at address <addr> ibm,chip-id : chip id where the RNG is @@ -27,21 +43,3 @@ reg : address of the register to read from Each read from the RNG register will provide a new random number. -NX 842 Coprocessor ------------------- - -This is the memory compression coprocessor, which uses the IBM proprietary -842 compression algorithm and format. Each node represents a unique 842 -coprocessor. The nodes are located at: - -/ibm,nx842-powernv#<chip-id> : 842 coprocessor on chip <chip-id> -ibm,chip-id : chip id where the 842 is -ibm,coprocessor-type : CT value common to all 842 coprocessors -ibm,coprocessor-instance : CI value unique to all 842 coprocessors - -Access to the coprocessor requires using the ICSWX instruction, which uses -a specific format including a Coprocessor Type (CT) and Coprocessor Instance (CI) -value to address each request to the right coprocessor. The system should -use the CT and CI values for a particular node to communicate with it. For -all 842 coprocessors in the system, the CT value will (should) be the same, -while each will have a different CI value. |