Home
last modified time | relevance | path

Searched +full:p9 +full:- +full:occ +full:- +full:hwmon (Results 1 – 11 of 11) sorted by relevance

/linux/Documentation/devicetree/bindings/fsi/
H A Dibm,p9-occ.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-occ.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached On-Chip Controller (OCC)
10 - Eddie James <eajames@linux.ibm.com>
13 The POWER processor On-Chip Controller (OCC) helps manage power and
14 thermals for the system, accessed through the FSI-attached SBEFIFO
20 - ibm,p9-occ
21 - ibm,p10-occ
[all …]
/linux/drivers/hwmon/occ/
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0-only
2 occ-hwmon-common-objs := common.o sysfs.o
3 occ-p8-hwmon-objs := p8_i2c.o
4 occ-p9-hwmon-objs := p9_sbe.o
6 obj-$(CONFIG_SENSORS_OCC) += occ-hwmon-common.o
7 obj-$(CONFIG_SENSORS_OCC_P8_I2C) += occ-p8-hwmon.o
8 obj-$(CONFIG_SENSORS_OCC_P9_SBE) += occ-p9-hwmon.o
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # On-Chip Controller configuration
7 tristate "POWER8 OCC through I2C"
12 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
14 the P8, not the POWER processor itself. Communications with the OCC are
18 called occ-p8-hwmon.
21 tristate "POWER9 OCC through SBE"
26 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
28 the P9, not the POWER processor itself. Communications with the OCC are
32 called occ-p9-hwmon.
/linux/Documentation/devicetree/bindings/hwmon/
H A Dibm,occ-hwmon.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/hwmon/ibm,occ-hwmon.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM On-Chip Controller (OCC) accessed from a service processor
10 - Eddie James <eajames@linux.ibm.com>
13 The POWER processor On-Chip Controller (OCC) helps manage power and
15 controller can query the OCC for it's power and thermal data to report
16 through hwmon.
21 - ibm,p9-occ-hwmon
[all …]
/linux/arch/arm/boot/dts/aspeed/
H A Dibm-power10-quad.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later
4 #include "ibm-power10-dual.dtsi"
8 compatible = "ibm,i2cr-fsi-master";
10 #address-cells = <2>;
11 #size-cells = <0>;
15 #address-cells = <1>;
16 #size-cells = <1>;
17 chip-id = <0>;
20 compatible = "ibm,i2cr-scom";
25 compatible = "ibm,p9-sbefifo";
[all …]
H A Dibm-power11-quad.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later
125 #address-cells = <2>;
126 #size-cells = <0>;
128 bus-frequency = <100000000>;
129 cfam-reset-gpios = <&gpio0 ASPEED_GPIO(Q, 0) GPIO_ACTIVE_HIGH>;
133 #address-cells = <1>;
134 #size-cells = <1>;
135 chip-id = <0>;
138 compatible = "ibm,p9-scom";
143 compatible = "ibm,i2c-fsi";
[all …]
H A Daspeed-bmc-ibm-everest.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include "aspeed-g6.dtsi"
6 #include <dt-bindings/gpio/aspeed-gpio.h>
7 #include <dt-bindings/i2c/i2c.h>
8 #include <dt-bindings/leds/leds-pca955x.h>
12 compatible = "ibm,everest-bmc", "aspeed,ast2600";
169 stdout-path = &uart5;
178 reserved-memory {
179 #address-cells = <1>;
[all …]
H A Daspeed-bmc-opp-tacoma.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include "aspeed-g6.dtsi"
6 #include <dt-bindings/gpio/aspeed-gpio.h>
7 #include <dt-bindings/i2c/i2c.h>
8 #include <dt-bindings/leds/leds-pca955x.h>
12 compatible = "ibm,tacoma-bmc", "aspeed,ast2600";
15 stdout-path = &uart5;
24 reserved-memory {
25 #address-cells = <1>;
[all …]
H A Daspeed-bmc-ibm-fuji.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include <dt-bindings/gpio/aspeed-gpio.h>
6 #include <dt-bindings/i2c/i2c.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include "aspeed-g6.dtsi"
9 #include "ibm-power11-quad.dtsi"
13 compatible = "ibm,fuji-bmc", "aspeed,ast2600";
170 stdout-path = &uart5;
178 reserved-memory {
[all …]
/linux/Documentation/hwmon/
H A Docc.rst1 Kernel driver occ-hwmon
12 -----------
14 This driver supports hardware monitoring for the On-Chip Controller (OCC)
15 embedded on POWER processors. The OCC is a device that collects and aggregates
16 sensor data from the processor and the system. The OCC can provide the raw
20 manually if an "ibm,p8-occ-hwmon" compatible device is found under the
21 appropriate I2C bus node in the device-tree.
23 The P9 version of this driver is a client driver of the FSI-based OCC driver.
24 It will be probed automatically by the FSI-based OCC driver.
27 -------------
[all …]
/linux/drivers/fsi/
H A Dfsi-occ.c1 // SPDX-License-Identifier: GPL-2.0
7 #include <linux/fsi-sbefifo.h>
16 #include <linux/fsi-occ.h>
42 struct occ { struct
58 #define to_occ(x) container_of((x), struct occ, mdev) argument
69 struct occ *occ; member
83 struct miscdevice *mdev = file->private_data; in occ_open()
84 struct occ *occ = to_occ(mdev); in occ_open() local
87 return -ENOMEM; in occ_open()
89 client->buffer = (u8 *)__get_free_page(GFP_KERNEL); in occ_open()
[all …]