10 FSI - the FRU Support Interface - is a simple bus for low-level
11 access to POWER-based hardware.
15 config FSI_NEW_DEV_NODE
16 bool "Create '/dev/fsi' directory for char devices"
19 This option causes char devices created for FSI devices to be
20 located under a common /dev/fsi/ directory. Set to N unless your
21 userspace has been updated to handle the new location.
23 Additionally, it also causes the char device names to be offset
24 by one so that chip 0 will have /dev/scom1 and chip1 /dev/scom2
25 to match old userspace expectations.
27 New userspace will use udev rules to generate predictable access
28 symlinks in /dev/fsi/by-path when this option is enabled.
30 config FSI_MASTER_GPIO
31 tristate "GPIO-based FSI master"
35 This option enables a FSI master driver using GPIO lines.
38 tristate "FSI hub master"
40 This option enables a FSI hub master driver. Hub is a type of FSI
41 master that is connected to the upstream master via a slave. Hubs
42 allow chaining of FSI links to an arbitrary depth. This allows for
43 a high target device fanout.
45 config FSI_MASTER_AST_CF
46 tristate "FSI master based on Aspeed ColdFire coprocessor"
48 depends on GPIO_ASPEED
50 This option enables a FSI master using the AST2400 and AST2500 GPIO
51 lines driven by the internal ColdFire coprocessor. This requires
52 the corresponding machine specific ColdFire firmware to be available.
55 tristate "SCOM FSI client device driver"
57 This option enables an FSI based SCOM device driver.
60 tristate "SBEFIFO FSI client device driver"
63 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
64 a pipe-like FSI device for communicating with the self boot engine
65 (SBE) on POWER processors.