xref: /openbmc/linux/drivers/fsi/Kconfig (revision 023e4163)
1#
2# FSI subsystem
3#
4
5menuconfig FSI
6	tristate "FSI support"
7	depends on OF
8	select CRC4
9	---help---
10	  FSI - the FRU Support Interface - is a simple bus for low-level
11	  access to POWER-based hardware.
12
13if FSI
14
15config FSI_NEW_DEV_NODE
16	bool "Create '/dev/fsi' directory for char devices"
17	default n
18	---help---
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.
22
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.
26
27	New userspace will use udev rules to generate predictable access
28	symlinks in /dev/fsi/by-path when this option is enabled.
29
30config FSI_MASTER_GPIO
31	tristate "GPIO-based FSI master"
32	depends on GPIOLIB
33	select CRC4
34	---help---
35	This option enables a FSI master driver using GPIO lines.
36
37config FSI_MASTER_HUB
38	tristate "FSI hub master"
39	---help---
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.
44
45config FSI_MASTER_AST_CF
46	tristate "FSI master based on Aspeed ColdFire coprocessor"
47	depends on GPIOLIB
48	depends on GPIO_ASPEED
49	select GENERIC_ALLOCATOR
50	---help---
51	This option enables a FSI master using the AST2400 and AST2500 GPIO
52	lines driven by the internal ColdFire coprocessor. This requires
53	the corresponding machine specific ColdFire firmware to be available.
54
55config FSI_SCOM
56	tristate "SCOM FSI client device driver"
57	---help---
58	This option enables an FSI based SCOM device driver.
59
60config FSI_SBEFIFO
61	tristate "SBEFIFO FSI client device driver"
62	depends on OF_ADDRESS
63	---help---
64	This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
65	a pipe-like FSI device for communicating with the self boot engine
66	(SBE) on POWER processors.
67
68config FSI_OCC
69	tristate "OCC SBEFIFO client device driver"
70	depends on FSI_SBEFIFO
71	---help---
72	This option enables an SBEFIFO based On-Chip Controller (OCC) device
73	driver. The OCC is a device embedded on a POWER processor that collects
74	and aggregates sensor data from the processor and system. The OCC can
75	provide the raw sensor data as well as perform thermal and power
76	management on the system.
77
78endif
79