| /Documentation/devicetree/bindings/tpm/ |
| D | ibm,vtpm.yaml | 4 $id: http://devicetree.org/schemas/tpm/ibm,vtpm.yaml#
7 title: IBM Virtual Trusted Platform Module (vTPM)
10 - Nayna Jain <nayna@linux.ibm.com>
13 Virtual TPM is used on IBM POWER7+ and POWER8 systems running POWERVM.
23 - IBM,vtpm
24 - IBM,vtpm20
30 - IBM,vtpm
31 - IBM,vtpm20
36 ibm,#dma-address-cells:
42 ibm,#dma-size-cells:
[all …]
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | power-mgt.txt | 1 IBM Power-Management Bindings
33 "ibm,cpu-idle-state-names" and "ibm,cpu-idle-state-flags" are
37 - ibm,cpu-idle-state-names:
40 - ibm,cpu-idle-state-flags:
60 - ibm,cpu-idle-state-latencies-ns:
63 ibm,cpu-idle-state-names.
65 - ibm,cpu-idle-state-residency-ns:
68 ibm,cpu-idle-state-names. On POWER8 this is an optional
73 - ibm,cpu-idle-state-psscr:
75 PSSCR for each of the idle states in ibm,cpu-idle-state-names.
[all …]
|
| D | sensor-groups.txt | 1 IBM OPAL Sensor Groups Binding
4 Node: /ibm,opal/sensor-groups
9 - compatible : Should be "ibm,opal-sensor-group"
20 - ibm,chip-id : Chip ID
22 - sensors : Phandle array of child nodes of /ibm,opal/sensor/
|
| /Documentation/devicetree/bindings/fsi/ |
| D | ibm,p9-occ.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,p9-occ.yaml#
7 title: IBM FSI-attached On-Chip Controller (OCC)
10 - Eddie James <eajames@linux.ibm.com>
20 - ibm,p9-occ
21 - ibm,p10-occ
25 $ref: /schemas/hwmon/ibm,occ-hwmon.yaml
35 compatible = "ibm,p9-occ";
38 compatible = "ibm,p9-occ-hwmon";
|
| D | ibm,p9-sbefifo.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,p9-sbefifo.yaml#
7 title: IBM FSI-attached SBEFIFO engine
10 - Eddie James <eajames@linux.ibm.com>
20 - ibm,p9-sbefifo
21 - ibm,odyssey-sbefifo
29 $ref: ibm,p9-occ.yaml#
40 compatible = "ibm,p9-sbefifo";
44 compatible = "ibm,p9-occ";
|
| D | ibm,p9-scom.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,p9-scom.yaml#
7 title: IBM FSI-attached SCOM engine
10 - Eddie James <eajames@linux.ibm.com>
19 - ibm,p9-scom
20 - ibm,i2cr-scom
35 compatible = "ibm,p9-scom";
|
| D | ibm,fsi2spi.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,fsi2spi.yaml#
7 title: IBM FSI-attached SPI controllers
10 - Eddie James <eajames@linux.ibm.com>
20 - ibm,fsi2spi
35 $ref: /schemas/spi/ibm,spi-fsi.yaml
46 compatible = "ibm,fsi2spi";
52 compatible = "ibm,spi-fsi";
|
| D | ibm,i2cr-fsi-master.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,i2cr-fsi-master.yaml#
7 title: IBM I2C Responder virtual FSI master
10 - Eddie James <eajames@linux.ibm.com>
20 - ibm,i2cr-fsi-master
41 compatible = "ibm,i2cr-fsi-master";
|
| D | ibm,p9-fsi-controller.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,p9-fsi-controller.yaml#
7 title: IBM FSI-attached FSI Hub Controller
10 - Eddie James <eajames@linux.ibm.com>
20 - ibm,p9-fsi-controller
34 compatible = "ibm,p9-fsi-controller";
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity
31 The “ibm,associativity” property contains a list of one or more numbers (domainID)
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
52 "ibm,associativity-reference-points" property, Form 2 allows a large number of primary domain
57 "ibm,architecture-vec-5" property.
59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing
61 used as an index while computing numa distance information via "ibm,numa-distance-table".
[all …]
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 2 IBM Akebono board device tree
5 The IBM Akebono board is a development board for the PPC476GTR SoC.
11 - model : "ibm,akebono".
12 - compatible : "ibm,akebono" , "ibm,476gtr".
20 - compatible : should be "ibm,476gtr-sdhci","generic-sdhci".
30 - compatible : should be "ibm,476gtr-ahci".
41 - compatible : should be "ibm,akebono-fpga".
51 - compatible : should be "ibm,akebono-avr".
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ibm,occ-hwmon.yaml | 4 $id: http://devicetree.org/schemas/hwmon/ibm,occ-hwmon.yaml#
7 title: IBM On-Chip Controller (OCC) accessed from a service processor
10 - Eddie James <eajames@linux.ibm.com>
21 - ibm,p9-occ-hwmon
22 - ibm,p10-occ-hwmon
24 ibm,no-poll-on-init:
37 compatible = "ibm,p10-occ-hwmon";
38 ibm,no-poll-on-init;
|
| D | ibm,opal-sensor.yaml | 4 $id: http://devicetree.org/schemas/hwmon/ibm,opal-sensor.yaml#
7 title: IBM POWERNV platform sensors
15 - ibm,opal-sensor-cooling-fan
16 - ibm,opal-sensor-amb-temp
17 - ibm,opal-sensor-power-supply
18 - ibm,opal-sensor-power
35 compatible = "ibm,opal-sensor-cooling-fan";
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 6 perspective, the properties of use are "ibm,port-name" and "ibm,opal-id".
11 - compatible: must be "ibm,opal-i2c"
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
18 - ibm,port-name: Firmware provides this name that uniquely identifies the i2c
30 compatible = "ibm,power8-i2c-port", "ibm,opal-i2c";
31 ibm,opal-id = <0x1>;
32 ibm,port-name = "p8_00000000_e1p0";
|
| /Documentation/ABI/testing/ |
| D | sysfs-secvar | 3 Contact: Nayna Jain <nayna@linux.ibm.com>
10 Contact: Nayna Jain <nayna@linux.ibm.com>
16 Contact: Nayna Jain <nayna@linux.ibm.com>
22 and is expected to be "ibm,edk2-compat-v1".
26 has the form "ibm,plpks-sb-v<version>", or
27 "ibm,plpks-sb-unknown" if there is no SB_VERSION variable.
31 Contact: Nayna Jain <nayna@linux.ibm.com>
39 Contact: Nayna Jain <nayna@linux.ibm.com>
45 Contact: Nayna Jain <nayna@linux.ibm.com>
51 Contact: Nayna Jain <nayna@linux.ibm.com>
[all …]
|
| D | debugfs-driver-genwqe | 3 Contact: haver@linux.vnet.ibm.com
8 Contact: haver@linux.vnet.ibm.com
14 Contact: haver@linux.vnet.ibm.com
20 Contact: haver@linux.vnet.ibm.com
26 Contact: haver@linux.vnet.ibm.com
32 Contact: haver@linux.vnet.ibm.com
39 Contact: haver@linux.vnet.ibm.com
45 Contact: haver@linux.vnet.ibm.com
51 Contact: haver@linux.vnet.ibm.com
57 Contact: haver@linux.vnet.ibm.com
[all …]
|
| D | sysfs-driver-genwqe | 3 Contact: haver@linux.vnet.ibm.com
9 Contact: haver@linux.vnet.ibm.com
15 Contact: haver@linux.vnet.ibm.com
20 Contact: haver@linux.vnet.ibm.com
25 Contact: haver@linux.vnet.ibm.com
30 Contact: klebers@linux.vnet.ibm.com
43 Contact: haver@linux.vnet.ibm.com
48 Contact: haver@linux.vnet.ibm.com
54 Contact: haver@linux.vnet.ibm.com
60 Contact: haver@linux.vnet.ibm.com
[all …]
|
| D | sysfs-class-cxl | 29 Users: https://github.com/ibm-capi/libcxl
39 Users: https://github.com/ibm-capi/libcxl
47 Users: https://github.com/ibm-capi/libcxl
55 Users: https://github.com/ibm-capi/libcxl
64 Users: https://github.com/ibm-capi/libcxl
85 Users: https://github.com/ibm-capi/libcxl
93 Users: https://github.com/ibm-capi/libcxl
100 Users: https://github.com/ibm-capi/libcxl
108 Users: https://github.com/ibm-capi/libcxl
122 Users: https://github.com/ibm-capi/libcxl
[all …]
|
| D | sysfs-devices-system-ibm-rtl | 4 Contact: Vernon Mauery <vernux@us.ibm.com>
12 Users: The ibm-prtm userspace daemon uses this interface.
18 Contact: Vernon Mauery <vernux@us.ibm.com>
22 Users: The ibm-prtm userspace daemon uses this interface.
|
| /Documentation/devicetree/bindings/arm/aspeed/ |
| D | aspeed.yaml | 50 - ibm,mihawk-bmc
51 - ibm,mowgli-bmc
52 - ibm,romulus-bmc
53 - ibm,swift-bmc
54 - ibm,witherspoon-bmc
90 - ibm,blueridge-bmc
91 - ibm,everest-bmc
92 - ibm,fuji-bmc
93 - ibm,rainier-bmc
94 - ibm,system1-bmc
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | ibm,op-panel.yaml | 4 $id: http://devicetree.org/schemas/input/ibm,op-panel.yaml#
7 title: IBM Operation Panel
10 - Eddie James <eajames@linux.ibm.com>
16 The IBM Operation Panel provides a simple interface to control the connected
22 const: ibm,op-panel
45 ibm-op-panel@62 {
46 compatible = "ibm,op-panel";
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,vas.txt | 1 * IBM Powerpc Virtual Accelerator Switchboard (VAS)
8 - compatible : should be "ibm,vas".
9 - ibm,vas-id : A unique identifier for each instance of VAS in the system
18 compatible = "ibm,vas", "ibm,power9-vas";
21 ibm,vas-id = <0x1>;
|
| /Documentation/devicetree/bindings/spi/ |
| D | ibm,spi-fsi.yaml | 4 $id: http://devicetree.org/schemas/spi/ibm,spi-fsi.yaml#
7 title: IBM FSI-attached SPI Controller
10 - Eddie James <eajames@linux.ibm.com>
13 A SPI controller found on IBM Power processors, accessed over FSI from a
14 service processor. This node will always be a child node of an ibm,fsi2spi
20 - ibm,spi-fsi
41 compatible = "ibm,spi-fsi";
|
| /Documentation/devicetree/bindings/ |
| D | incomplete-devices.yaml | 168 - IBM,CBEA
169 - IBM,lhca
170 - IBM,lhea
171 - IBM,lhea-ethernet
172 - ibm,axon-msic
268 - ibm,axon-msic
269 - ibm,pmemory
270 - ibm,pmemory-v2
271 - ibm,power-rng
272 - ibm,ppc4xx-spi
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | ibm,emac.txt | 3 The EMAC ethernet controller in IBM and AMCC 4xx chips, and also
16 "ibm,emac-CHIP" where CHIP is the host ASIC (440gx,
17 405gp, Axon) and second is either "ibm,emac" or
18 "ibm,emac4". For Axon, thus, we have: "ibm,emac-axon",
19 "ibm,emac4"
105 compatible = "ibm,emac-440gp", "ibm,emac";
125 compatible = "ibm,emac-apm821xx", "ibm,emac4sync";
170 "ibm,mcmal-CHIP" where CHIP is the host ASIC (like
171 emac) and the second is either "ibm,mcmal" or
172 "ibm,mcmal2".
[all …]
|