Home
last modified time | relevance | path

Searched +full:p9 +full:- +full:fsi +full:- +full:controller (Results 1 – 9 of 9) sorted by relevance

/linux-6.12.1/Documentation/devicetree/bindings/fsi/
Dibm,p9-fsi-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-fsi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached FSI Hub Controller
10 - Eddie James <eajames@linux.ibm.com>
13 The FSI Hub Controller is an FSI controller, providing a number of FSI links,
14 located on a CFAM. Therefore this node will always be a child of an FSI CFAM
20 - ibm,p9-fsi-controller
24 - description: FSI slave address
[all …]
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-6.12.1/arch/arm/boot/dts/aspeed/
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 …]
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 …]
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 …]
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 …]
Dibm-power10-dual.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later
7 #address-cells = <2>;
8 #size-cells = <0>;
10 cfam-reset-gpios = <&gpio0 ASPEED_GPIO(Q, 0) GPIO_ACTIVE_HIGH>;
14 #address-cells = <1>;
15 #size-cells = <1>;
16 chip-id = <0>;
24 compatible = "ibm,fsi-i2c-master";
26 #address-cells = <1>;
27 #size-cells = <0>;
[all …]
/linux-6.12.1/drivers/hwmon/occ/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # On-Chip Controller configuration
12 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
13 can only run on a baseboard management controller (BMC) connected to
18 called occ-p8-hwmon.
26 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
27 can only run on a baseboard management controller (BMC) connected to
28 the P9, not the POWER processor itself. Communications with the OCC are
29 established through SBE fifo on an FSI bus.
32 called occ-p9-hwmon.
/linux-6.12.1/Documentation/hwmon/
Docc.rst1 Kernel driver occ-hwmon
12 -----------
14 This driver supports hardware monitoring for the On-Chip Controller (OCC)
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 -------------
29 The following attributes are supported. All attributes are read-only unless
35 to the device driver, which must therefore export the sensor ID as-is.
[all …]