.. | .. |
---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
---|
1 | 2 | # |
---|
2 | 3 | # FSI subsystem |
---|
3 | 4 | # |
---|
.. | .. |
---|
6 | 7 | tristate "FSI support" |
---|
7 | 8 | depends on OF |
---|
8 | 9 | select CRC4 |
---|
9 | | - ---help--- |
---|
| 10 | + help |
---|
10 | 11 | FSI - the FRU Support Interface - is a simple bus for low-level |
---|
11 | 12 | access to POWER-based hardware. |
---|
12 | 13 | |
---|
.. | .. |
---|
15 | 16 | config FSI_NEW_DEV_NODE |
---|
16 | 17 | bool "Create '/dev/fsi' directory for char devices" |
---|
17 | 18 | default n |
---|
18 | | - ---help--- |
---|
| 19 | + help |
---|
19 | 20 | This option causes char devices created for FSI devices to be |
---|
20 | 21 | located under a common /dev/fsi/ directory. Set to N unless your |
---|
21 | 22 | userspace has been updated to handle the new location. |
---|
.. | .. |
---|
31 | 32 | tristate "GPIO-based FSI master" |
---|
32 | 33 | depends on GPIOLIB |
---|
33 | 34 | select CRC4 |
---|
34 | | - ---help--- |
---|
| 35 | + help |
---|
35 | 36 | This option enables a FSI master driver using GPIO lines. |
---|
36 | 37 | |
---|
37 | 38 | config FSI_MASTER_HUB |
---|
38 | 39 | tristate "FSI hub master" |
---|
39 | | - ---help--- |
---|
| 40 | + help |
---|
40 | 41 | This option enables a FSI hub master driver. Hub is a type of FSI |
---|
41 | 42 | master that is connected to the upstream master via a slave. Hubs |
---|
42 | 43 | allow chaining of FSI links to an arbitrary depth. This allows for |
---|
.. | .. |
---|
47 | 48 | depends on GPIOLIB |
---|
48 | 49 | depends on GPIO_ASPEED |
---|
49 | 50 | select GENERIC_ALLOCATOR |
---|
50 | | - ---help--- |
---|
| 51 | + help |
---|
51 | 52 | This option enables a FSI master using the AST2400 and AST2500 GPIO |
---|
52 | 53 | lines driven by the internal ColdFire coprocessor. This requires |
---|
53 | 54 | the corresponding machine specific ColdFire firmware to be available. |
---|
54 | 55 | |
---|
| 56 | +config FSI_MASTER_ASPEED |
---|
| 57 | + tristate "FSI ASPEED master" |
---|
| 58 | + depends on HAS_IOMEM |
---|
| 59 | + help |
---|
| 60 | + This option enables a FSI master that is present behind an OPB bridge |
---|
| 61 | + in the AST2600. |
---|
| 62 | + |
---|
| 63 | + Enable it for your BMC kernel in an OpenPower or IBM Power system. |
---|
| 64 | + |
---|
55 | 65 | config FSI_SCOM |
---|
56 | 66 | tristate "SCOM FSI client device driver" |
---|
57 | | - ---help--- |
---|
| 67 | + help |
---|
58 | 68 | This option enables an FSI based SCOM device driver. |
---|
59 | 69 | |
---|
60 | 70 | config FSI_SBEFIFO |
---|
61 | 71 | tristate "SBEFIFO FSI client device driver" |
---|
62 | 72 | depends on OF_ADDRESS |
---|
63 | | - ---help--- |
---|
| 73 | + help |
---|
64 | 74 | This option enables an FSI based SBEFIFO device driver. The SBEFIFO is |
---|
65 | 75 | a pipe-like FSI device for communicating with the self boot engine |
---|
66 | 76 | (SBE) on POWER processors. |
---|
67 | 77 | |
---|
| 78 | +config FSI_OCC |
---|
| 79 | + tristate "OCC SBEFIFO client device driver" |
---|
| 80 | + depends on FSI_SBEFIFO |
---|
| 81 | + help |
---|
| 82 | + This option enables an SBEFIFO based On-Chip Controller (OCC) device |
---|
| 83 | + driver. The OCC is a device embedded on a POWER processor that collects |
---|
| 84 | + and aggregates sensor data from the processor and system. The OCC can |
---|
| 85 | + provide the raw sensor data as well as perform thermal and power |
---|
| 86 | + management on the system. |
---|
| 87 | + |
---|
68 | 88 | endif |
---|