Kconfig 2.6 KB

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