diff options
| author | Anju T Sudhakar <anju@linux.vnet.ibm.com> | 2019-03-22 12:13:47 +0530 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.ibm.com> | 2019-03-28 15:24:13 +1100 |
| commit | 09e9121090703d828d2e122043513e9dca49a7c4 (patch) | |
| tree | 678f4081133533276d2301f5044b3b658de43fda | |
| parent | 6d9a87cec05ab7f5bc48d4c26c6877108061330a (diff) | |
| download | blackbird-skiboot-09e9121090703d828d2e122043513e9dca49a7c4.tar.gz blackbird-skiboot-09e9121090703d828d2e122043513e9dca49a7c4.zip | |
doc/device-tree: Edit device tree documentation for imc to include trace-node information.
Add trace-node information in the device-tree document for IMC.
Signed-off-by: Anju T Sudhakar <anju@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
| -rw-r--r-- | doc/device-tree/imc.rst | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/doc/device-tree/imc.rst b/doc/device-tree/imc.rst index 8533cc12..6046b459 100644 --- a/doc/device-tree/imc.rst +++ b/doc/device-tree/imc.rst @@ -46,6 +46,14 @@ IMC device/units bindings chipids = <chip-id for the base_addr > }; + trace@0 { + compatible = "ibm,imc-counters"; + events-prefix = "trace_"; + reg = <0x0 0x8>; + events = < &TRACE_IMC >; + type = <0x2>; + size = <0x40000>; + }; IMC device event bindings ------------------------- @@ -70,3 +78,45 @@ IMC device event bindings /* List of events supported */ }; + + TRACE_IMC: trace-events { + #address-cells = <0x1>; + #size-cells = <0x1>; + + event@10200000 { + event-name = "cycles" ; /* For trace node, we only have cycles event now */ + reg = <0x10200000 0x8>; + desc = "Reference cycles" ; + }; + }; + +Trace-mode SCOM +---------------- + +Trace scom is a 64 bit value which contains the event information for +IMC-trace mode. Following is the trace-scom layout. + +**TRACE_IMC_SCOM bit representation** + +:0-1: SAMPSEL + +:2-33: CPMC_LOAD + +:34-40: CPMC1SEL + +:41-47: CPMC2SEL + +:48-50: BUFFERSIZE + +:51-63: RESERVED + +*CPMC_LOAD* contains the sampling duration. *SAMPSEL* and *CPMC*SEL* +determines the event to count. *BUFFRSIZE* indicates the memory range. + +*BUFFERSIZE* can be +:: + b’000’ - 4K entries * 64 per entry = 256K + b’001’ - 8K entries * 64 per entry = 512K + b’010’ - 16K entries * 64 per entry = 1M + b’011’ - 32K entries * 64 per entry = 2M + b’100’ - 64K entries * 64 per entry = 4M |
