Kconfig 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122
  1. #
  2. # PMBus chip drivers configuration
  3. #
  4. menuconfig PMBUS
  5. tristate "PMBus support"
  6. depends on I2C && EXPERIMENTAL
  7. default n
  8. help
  9. Say yes here if you want to enable PMBus support.
  10. This driver can also be built as a module. If so, the module will
  11. be called pmbus_core.
  12. if PMBUS
  13. config SENSORS_PMBUS
  14. tristate "Generic PMBus devices"
  15. default y
  16. help
  17. If you say yes here you get hardware monitoring support for generic
  18. PMBus devices, including but not limited to ADP4000, BMR450, BMR451,
  19. BMR453, BMR454, NCP4200, and NCP4208.
  20. This driver can also be built as a module. If so, the module will
  21. be called pmbus.
  22. config SENSORS_ADM1275
  23. tristate "Analog Devices ADM1275 and compatibles"
  24. default n
  25. help
  26. If you say yes here you get hardware monitoring support for Analog
  27. Devices ADM1275 and ADM1276 Hot-Swap Controller and Digital Power
  28. Monitor.
  29. This driver can also be built as a module. If so, the module will
  30. be called adm1275.
  31. config SENSORS_LM25066
  32. tristate "National Semiconductor LM25066 and compatibles"
  33. default n
  34. help
  35. If you say yes here you get hardware monitoring support for National
  36. Semiconductor LM25066, LM5064, and LM5066.
  37. This driver can also be built as a module. If so, the module will
  38. be called lm25066.
  39. config SENSORS_LTC2978
  40. tristate "Linear Technologies LTC2978 and LTC3880"
  41. default n
  42. help
  43. If you say yes here you get hardware monitoring support for Linear
  44. Technology LTC2978 and LTC3880.
  45. This driver can also be built as a module. If so, the module will
  46. be called ltc2978.
  47. config SENSORS_MAX16064
  48. tristate "Maxim MAX16064"
  49. default n
  50. help
  51. If you say yes here you get hardware monitoring support for Maxim
  52. MAX16064.
  53. This driver can also be built as a module. If so, the module will
  54. be called max16064.
  55. config SENSORS_MAX34440
  56. tristate "Maxim MAX34440/MAX34441"
  57. default n
  58. help
  59. If you say yes here you get hardware monitoring support for Maxim
  60. MAX34440 and MAX34441.
  61. This driver can also be built as a module. If so, the module will
  62. be called max34440.
  63. config SENSORS_MAX8688
  64. tristate "Maxim MAX8688"
  65. default n
  66. help
  67. If you say yes here you get hardware monitoring support for Maxim
  68. MAX8688.
  69. This driver can also be built as a module. If so, the module will
  70. be called max8688.
  71. config SENSORS_UCD9000
  72. tristate "TI UCD90120, UCD90124, UCD9090, UCD90910"
  73. default n
  74. help
  75. If you say yes here you get hardware monitoring support for TI
  76. UCD90120, UCD90124, UCD9090, UCD90910 Sequencer and System Health
  77. Controllers.
  78. This driver can also be built as a module. If so, the module will
  79. be called ucd9000.
  80. config SENSORS_UCD9200
  81. tristate "TI UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, UCD9248"
  82. default n
  83. help
  84. If you say yes here you get hardware monitoring support for TI
  85. UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and UCD9248
  86. Digital PWM System Controllers.
  87. This driver can also be built as a module. If so, the module will
  88. be called ucd9200.
  89. config SENSORS_ZL6100
  90. tristate "Intersil ZL6100 and compatibles"
  91. default n
  92. help
  93. If you say yes here you get hardware monitoring support for Intersil
  94. ZL2004, ZL2006, ZL2008, ZL2105, ZL2106, ZL6100, and ZL6105 Digital
  95. DC/DC Controllers.
  96. This driver can also be built as a module. If so, the module will
  97. be called zl6100.
  98. endif # PMBUS