Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494
  1. #
  2. # Sensor device configuration
  3. #
  4. menu "I2C Hardware Bus support"
  5. depends on I2C
  6. config I2C_ALI1535
  7. tristate "ALI 1535"
  8. depends on I2C && PCI
  9. help
  10. If you say yes to this option, support will be included for the SMB
  11. Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
  12. controller is part of the 7101 device, which is an ACPI-compliant
  13. Power Management Unit (PMU).
  14. This driver can also be built as a module. If so, the module
  15. will be called i2c-ali1535.
  16. config I2C_ALI1563
  17. tristate "ALI 1563"
  18. depends on I2C && PCI && EXPERIMENTAL
  19. help
  20. If you say yes to this option, support will be included for the SMB
  21. Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
  22. controller is part of the 7101 device, which is an ACPI-compliant
  23. Power Management Unit (PMU).
  24. This driver can also be built as a module. If so, the module
  25. will be called i2c-ali1563.
  26. config I2C_ALI15X3
  27. tristate "ALI 15x3"
  28. depends on I2C && PCI
  29. help
  30. If you say yes to this option, support will be included for the
  31. Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
  32. This driver can also be built as a module. If so, the module
  33. will be called i2c-ali15x3.
  34. config I2C_AMD756
  35. tristate "AMD 756/766/768/8111 and nVidia nForce"
  36. depends on I2C && PCI
  37. help
  38. If you say yes to this option, support will be included for the AMD
  39. 756/766/768 mainboard I2C interfaces. The driver also includes
  40. support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
  41. the nVidia nForce I2C interface.
  42. This driver can also be built as a module. If so, the module
  43. will be called i2c-amd756.
  44. config I2C_AMD756_S4882
  45. tristate "SMBus multiplexing on the Tyan S4882"
  46. depends on I2C_AMD756 && EXPERIMENTAL
  47. help
  48. Enabling this option will add specific SMBus support for the Tyan
  49. S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
  50. over 8 different channels, where the various memory module EEPROMs
  51. and temperature sensors live. Saying yes here will give you access
  52. to these in addition to the trunk.
  53. This driver can also be built as a module. If so, the module
  54. will be called i2c-amd756-s4882.
  55. config I2C_AMD8111
  56. tristate "AMD 8111"
  57. depends on I2C && PCI
  58. help
  59. If you say yes to this option, support will be included for the
  60. second (SMBus 2.0) AMD 8111 mainboard I2C interface.
  61. This driver can also be built as a module. If so, the module
  62. will be called i2c-amd8111.
  63. config I2C_AU1550
  64. tristate "Au1550 SMBus interface"
  65. depends on I2C && SOC_AU1550
  66. help
  67. If you say yes to this option, support will be included for the
  68. Au1550 SMBus interface.
  69. This driver can also be built as a module. If so, the module
  70. will be called i2c-au1550.
  71. config I2C_ELEKTOR
  72. tristate "Elektor ISA card"
  73. depends on I2C && ISA && BROKEN_ON_SMP
  74. select I2C_ALGOPCF
  75. help
  76. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  77. such an adapter.
  78. This support is also available as a module. If so, the module
  79. will be called i2c-elektor.
  80. config I2C_HYDRA
  81. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  82. depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
  83. select I2C_ALGOBIT
  84. help
  85. This supports the use of the I2C interface in the Apple Hydra Mac
  86. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  87. have such a machine.
  88. This support is also available as a module. If so, the module
  89. will be called i2c-hydra.
  90. config I2C_I801
  91. tristate "Intel 82801 (ICH)"
  92. depends on I2C && PCI
  93. help
  94. If you say yes to this option, support will be included for the Intel
  95. 801 family of mainboard I2C interfaces. Specifically, the following
  96. versions of the chipset are supported:
  97. 82801AA
  98. 82801AB
  99. 82801BA
  100. 82801CA/CAM
  101. 82801DB
  102. 82801EB/ER (ICH5/ICH5R)
  103. 6300ESB
  104. ICH6
  105. ICH7
  106. ESB2
  107. This driver can also be built as a module. If so, the module
  108. will be called i2c-i801.
  109. config I2C_I810
  110. tristate "Intel 810/815"
  111. depends on I2C && PCI
  112. select I2C_ALGOBIT
  113. help
  114. If you say yes to this option, support will be included for the Intel
  115. 810/815 family of mainboard I2C interfaces. Specifically, the
  116. following versions of the chipset is supported:
  117. i810AA
  118. i810AB
  119. i810E
  120. i815
  121. This driver can also be built as a module. If so, the module
  122. will be called i2c-i810.
  123. config I2C_PIIX4
  124. tristate "Intel PIIX4"
  125. depends on I2C && PCI
  126. help
  127. If you say yes to this option, support will be included for the Intel
  128. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  129. versions of the chipset are supported:
  130. Intel PIIX4
  131. Intel 440MX
  132. Serverworks OSB4
  133. Serverworks CSB5
  134. Serverworks CSB6
  135. SMSC Victory66
  136. This driver can also be built as a module. If so, the module
  137. will be called i2c-piix4.
  138. config I2C_IBM_IIC
  139. tristate "IBM PPC 4xx on-chip I2C interface"
  140. depends on IBM_OCP && I2C
  141. help
  142. Say Y here if you want to use IIC peripheral found on
  143. embedded IBM PPC 4xx based systems.
  144. This driver can also be built as a module. If so, the module
  145. will be called i2c-ibm_iic.
  146. config I2C_IOP3XX
  147. tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
  148. depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
  149. help
  150. Say Y here if you want to use the IIC bus controller on
  151. the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
  152. This driver can also be built as a module. If so, the module
  153. will be called i2c-iop3xx.
  154. config I2C_ISA
  155. tristate
  156. depends on I2C
  157. config I2C_ITE
  158. tristate "ITE I2C Adapter"
  159. depends on I2C && MIPS_ITE8172
  160. select I2C_ALGOITE
  161. help
  162. This supports the ITE8172 I2C peripheral found on some MIPS
  163. systems. Say Y if you have one of these. You should also say Y for
  164. the ITE I2C driver algorithm support above.
  165. This support is also available as a module. If so, the module
  166. will be called i2c-ite.
  167. config I2C_IXP4XX
  168. tristate "IXP4xx GPIO-Based I2C Interface"
  169. depends on I2C && ARCH_IXP4XX
  170. select I2C_ALGOBIT
  171. help
  172. Say Y here if you have an Intel IXP4xx(420,421,422,425) based
  173. system and are using GPIO lines for an I2C bus.
  174. This support is also available as a module. If so, the module
  175. will be called i2c-ixp4xx.
  176. config I2C_IXP2000
  177. tristate "IXP2000 GPIO-Based I2C Interface"
  178. depends on I2C && ARCH_IXP2000
  179. select I2C_ALGOBIT
  180. help
  181. Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
  182. system and are using GPIO lines for an I2C bus.
  183. This support is also available as a module. If so, the module
  184. will be called i2c-ixp2000.
  185. config I2C_KEYWEST
  186. tristate "Powermac Keywest I2C interface"
  187. depends on I2C && PPC_PMAC
  188. help
  189. This supports the use of the I2C interface in the combo-I/O
  190. chip on recent Apple machines. Say Y if you have such a machine.
  191. This support is also available as a module. If so, the module
  192. will be called i2c-keywest.
  193. config I2C_MPC
  194. tristate "MPC107/824x/85xx/52xx"
  195. depends on I2C && PPC32
  196. help
  197. If you say yes to this option, support will be included for the
  198. built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
  199. MPC85xx family processors. The driver may also work on 52xx
  200. family processors, though interrupts are known not to work.
  201. This driver can also be built as a module. If so, the module
  202. will be called i2c-mpc.
  203. config I2C_NFORCE2
  204. tristate "Nvidia nForce2, nForce3 and nForce4"
  205. depends on I2C && PCI
  206. help
  207. If you say yes to this option, support will be included for the Nvidia
  208. nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
  209. This driver can also be built as a module. If so, the module
  210. will be called i2c-nforce2.
  211. config I2C_PARPORT
  212. tristate "Parallel port adapter"
  213. depends on I2C && PARPORT
  214. select I2C_ALGOBIT
  215. help
  216. This supports parallel port I2C adapters such as the ones made by
  217. Philips or Velleman, Analog Devices evaluation boards, and more.
  218. Basically any adapter using the parallel port as an I2C bus with
  219. no extra chipset is supported by this driver, or could be.
  220. This driver is a replacement for (and was inspired by) an older
  221. driver named i2c-philips-par. The new driver supports more devices,
  222. and makes it easier to add support for new devices.
  223. Another driver exists, named i2c-parport-light, which doesn't depend
  224. on the parport driver. This is meant for embedded systems. Don't say
  225. Y here if you intend to say Y or M there.
  226. This support is also available as a module. If so, the module
  227. will be called i2c-parport.
  228. config I2C_PARPORT_LIGHT
  229. tristate "Parallel port adapter (light)"
  230. depends on I2C
  231. select I2C_ALGOBIT
  232. help
  233. This supports parallel port I2C adapters such as the ones made by
  234. Philips or Velleman, Analog Devices evaluation boards, and more.
  235. Basically any adapter using the parallel port as an I2C bus with
  236. no extra chipset is supported by this driver, or could be.
  237. This driver is a light version of i2c-parport. It doesn't depend
  238. on the parport driver, and uses direct I/O access instead. This
  239. might be prefered on embedded systems where wasting memory for
  240. the clean but heavy parport handling is not an option. The
  241. drawback is a reduced portability and the impossibility to
  242. dasiy-chain other parallel port devices.
  243. Don't say Y here if you said Y or M to i2c-parport. Saying M to
  244. both is possible but both modules should not be loaded at the same
  245. time.
  246. This support is also available as a module. If so, the module
  247. will be called i2c-parport-light.
  248. config I2C_PROSAVAGE
  249. tristate "S3/VIA (Pro)Savage"
  250. depends on I2C && PCI
  251. select I2C_ALGOBIT
  252. help
  253. If you say yes to this option, support will be included for the
  254. I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
  255. graphics processors.
  256. chipsets supported:
  257. S3/VIA KM266/VT8375 aka ProSavage8
  258. S3/VIA KM133/VT8365 aka Savage4
  259. This support is also available as a module. If so, the module
  260. will be called i2c-prosavage.
  261. config I2C_RPXLITE
  262. tristate "Embedded Planet RPX Lite/Classic support"
  263. depends on (RPXLITE || RPXCLASSIC) && I2C
  264. select I2C_ALGO8XX
  265. config I2C_S3C2410
  266. tristate "S3C2410 I2C Driver"
  267. depends on I2C && ARCH_S3C2410
  268. help
  269. Say Y here to include support for I2C controller in the
  270. Samsung S3C2410 based System-on-Chip devices.
  271. config I2C_SAVAGE4
  272. tristate "S3 Savage 4"
  273. depends on I2C && PCI && EXPERIMENTAL
  274. select I2C_ALGOBIT
  275. help
  276. If you say yes to this option, support will be included for the
  277. S3 Savage 4 I2C interface.
  278. This driver can also be built as a module. If so, the module
  279. will be called i2c-savage4.
  280. config I2C_SIBYTE
  281. tristate "SiByte SMBus interface"
  282. depends on SIBYTE_SB1xxx_SOC && I2C
  283. help
  284. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  285. config SCx200_I2C
  286. tristate "NatSemi SCx200 I2C using GPIO pins"
  287. depends on SCx200_GPIO && I2C
  288. select I2C_ALGOBIT
  289. help
  290. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  291. If you don't know what to do here, say N.
  292. This support is also available as a module. If so, the module
  293. will be called scx200_i2c.
  294. config SCx200_I2C_SCL
  295. int "GPIO pin used for SCL"
  296. depends on SCx200_I2C
  297. default "12"
  298. help
  299. Enter the GPIO pin number used for the SCL signal. This value can
  300. also be specified with a module parameter.
  301. config SCx200_I2C_SDA
  302. int "GPIO pin used for SDA"
  303. depends on SCx200_I2C
  304. default "13"
  305. help
  306. Enter the GPIO pin number used for the SSA signal. This value can
  307. also be specified with a module parameter.
  308. config SCx200_ACB
  309. tristate "NatSemi SCx200 ACCESS.bus"
  310. depends on I2C && PCI
  311. help
  312. Enable the use of the ACCESS.bus controllers of a SCx200 processor.
  313. If you don't know what to do here, say N.
  314. This support is also available as a module. If so, the module
  315. will be called scx200_acb.
  316. config I2C_SIS5595
  317. tristate "SiS 5595"
  318. depends on I2C && PCI
  319. help
  320. If you say yes to this option, support will be included for the
  321. SiS5595 SMBus (a subset of I2C) interface.
  322. This driver can also be built as a module. If so, the module
  323. will be called i2c-sis5595.
  324. config I2C_SIS630
  325. tristate "SiS 630/730"
  326. depends on I2C && PCI
  327. help
  328. If you say yes to this option, support will be included for the
  329. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  330. This driver can also be built as a module. If so, the module
  331. will be called i2c-sis630.
  332. config I2C_SIS96X
  333. tristate "SiS 96x"
  334. depends on I2C && PCI
  335. help
  336. If you say yes to this option, support will be included for the SiS
  337. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  338. chipsets are supported:
  339. 645/961
  340. 645DX/961
  341. 645DX/962
  342. 648/961
  343. 650/961
  344. 735
  345. 745
  346. This driver can also be built as a module. If so, the module
  347. will be called i2c-sis96x.
  348. config I2C_STUB
  349. tristate "I2C/SMBus Test Stub"
  350. depends on I2C && EXPERIMENTAL && 'm'
  351. default 'n'
  352. help
  353. This module may be useful to developers of SMBus client drivers,
  354. especially for certain kinds of sensor chips.
  355. If you do build this module, be sure to read the notes and warnings
  356. in <file:Documentation/i2c/i2c-stub>.
  357. If you don't know what to do here, definitely say N.
  358. config I2C_VIA
  359. tristate "VIA 82C586B"
  360. depends on I2C && PCI && EXPERIMENTAL
  361. select I2C_ALGOBIT
  362. help
  363. If you say yes to this option, support will be included for the VIA
  364. 82C586B I2C interface
  365. This driver can also be built as a module. If so, the module
  366. will be called i2c-via.
  367. config I2C_VIAPRO
  368. tristate "VIA 82C596/82C686/823x"
  369. depends on I2C && PCI
  370. help
  371. If you say yes to this option, support will be included for the VIA
  372. 82C596/82C686/823x I2C interfaces. Specifically, the following
  373. chipsets are supported:
  374. 82C596A/B
  375. 82C686A/B
  376. 8231
  377. 8233
  378. 8233A
  379. 8235
  380. 8237
  381. This driver can also be built as a module. If so, the module
  382. will be called i2c-viapro.
  383. config I2C_VOODOO3
  384. tristate "Voodoo 3"
  385. depends on I2C && PCI
  386. select I2C_ALGOBIT
  387. help
  388. If you say yes to this option, support will be included for the
  389. Voodoo 3 I2C interface.
  390. This driver can also be built as a module. If so, the module
  391. will be called i2c-voodoo3.
  392. config I2C_PCA_ISA
  393. tristate "PCA9564 on an ISA bus"
  394. depends on I2C
  395. select I2C_ALGOPCA
  396. help
  397. This driver supports ISA boards using the Philips PCA 9564
  398. Parallel bus to I2C bus controller
  399. This driver can also be built as a module. If so, the module
  400. will be called i2c-pca-isa.
  401. config I2C_MV64XXX
  402. tristate "Marvell mv64xxx I2C Controller"
  403. depends on I2C && MV64X60 && EXPERIMENTAL
  404. help
  405. If you say yes to this option, support will be included for the
  406. built-in I2C interface on the Marvell 64xxx line of host bridges.
  407. This driver can also be built as a module. If so, the module
  408. will be called i2c-mv64xxx.
  409. endmenu