]>
Commit | Line | Data |
---|---|---|
ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
0508ad1f JK |
2 | # |
3 | # FSI subsystem | |
4 | # | |
5 | ||
baa8b941 | 6 | menuconfig FSI |
0508ad1f | 7 | tristate "FSI support" |
f6a2f8eb | 8 | depends on OF |
2b545cd8 | 9 | select CRC4 |
0508ad1f JK |
10 | ---help--- |
11 | FSI - the FRU Support Interface - is a simple bus for low-level | |
12 | access to POWER-based hardware. | |
ac0385d9 CB |
13 | |
14 | if FSI | |
15 | ||
0ab5fe53 BH |
16 | config FSI_NEW_DEV_NODE |
17 | bool "Create '/dev/fsi' directory for char devices" | |
18 | default n | |
19 | ---help--- | |
20 | This option causes char devices created for FSI devices to be | |
21 | located under a common /dev/fsi/ directory. Set to N unless your | |
22 | userspace has been updated to handle the new location. | |
23 | ||
24 | Additionally, it also causes the char device names to be offset | |
25 | by one so that chip 0 will have /dev/scom1 and chip1 /dev/scom2 | |
26 | to match old userspace expectations. | |
27 | ||
28 | New userspace will use udev rules to generate predictable access | |
29 | symlinks in /dev/fsi/by-path when this option is enabled. | |
30 | ||
ac0385d9 CB |
31 | config FSI_MASTER_GPIO |
32 | tristate "GPIO-based FSI master" | |
33 | depends on GPIOLIB | |
34 | select CRC4 | |
35 | ---help--- | |
36 | This option enables a FSI master driver using GPIO lines. | |
37 | ||
7f9e8f76 CB |
38 | config FSI_MASTER_HUB |
39 | tristate "FSI hub master" | |
40 | ---help--- | |
41 | This option enables a FSI hub master driver. Hub is a type of FSI | |
42 | master that is connected to the upstream master via a slave. Hubs | |
43 | allow chaining of FSI links to an arbitrary depth. This allows for | |
44 | a high target device fanout. | |
45 | ||
6a794a27 BH |
46 | config FSI_MASTER_AST_CF |
47 | tristate "FSI master based on Aspeed ColdFire coprocessor" | |
48 | depends on GPIOLIB | |
49 | depends on GPIO_ASPEED | |
64999fa7 | 50 | select GENERIC_ALLOCATOR |
6a794a27 BH |
51 | ---help--- |
52 | This option enables a FSI master using the AST2400 and AST2500 GPIO | |
53 | lines driven by the internal ColdFire coprocessor. This requires | |
54 | the corresponding machine specific ColdFire firmware to be available. | |
55 | ||
606397d6 JS |
56 | config FSI_MASTER_ASPEED |
57 | tristate "FSI ASPEED master" | |
58 | help | |
59 | This option enables a FSI master that is present behind an OPB bridge | |
60 | in the AST2600. | |
61 | ||
62 | Enable it for your BMC kernel in an OpenPower or IBM Power system. | |
63 | ||
680ca6dc CB |
64 | config FSI_SCOM |
65 | tristate "SCOM FSI client device driver" | |
66 | ---help--- | |
67 | This option enables an FSI based SCOM device driver. | |
68 | ||
9f4a8a2d BH |
69 | config FSI_SBEFIFO |
70 | tristate "SBEFIFO FSI client device driver" | |
32f7f89d | 71 | depends on OF_ADDRESS |
9f4a8a2d BH |
72 | ---help--- |
73 | This option enables an FSI based SBEFIFO device driver. The SBEFIFO is | |
74 | a pipe-like FSI device for communicating with the self boot engine | |
75 | (SBE) on POWER processors. | |
76 | ||
7ed98ddd EJ |
77 | config FSI_OCC |
78 | tristate "OCC SBEFIFO client device driver" | |
79 | depends on FSI_SBEFIFO | |
80 | ---help--- | |
81 | This option enables an SBEFIFO based On-Chip Controller (OCC) device | |
82 | driver. The OCC is a device embedded on a POWER processor that collects | |
83 | and aggregates sensor data from the processor and system. The OCC can | |
84 | provide the raw sensor data as well as perform thermal and power | |
85 | management on the system. | |
86 | ||
ac0385d9 | 87 | endif |