Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500
  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 "ISA Bus support"
  156. depends on I2C
  157. help
  158. If you say yes to this option, support will be included for i2c
  159. interfaces that are on the ISA bus.
  160. This driver can also be built as a module. If so, the module
  161. will be called i2c-isa.
  162. config I2C_ITE
  163. tristate "ITE I2C Adapter"
  164. depends on I2C && MIPS_ITE8172
  165. select I2C_ALGOITE
  166. help
  167. This supports the ITE8172 I2C peripheral found on some MIPS
  168. systems. Say Y if you have one of these. You should also say Y for
  169. the ITE I2C driver algorithm support above.
  170. This support is also available as a module. If so, the module
  171. will be called i2c-ite.
  172. config I2C_IXP4XX
  173. tristate "IXP4xx GPIO-Based I2C Interface"
  174. depends on I2C && ARCH_IXP4XX
  175. select I2C_ALGOBIT
  176. help
  177. Say Y here if you have an Intel IXP4xx(420,421,422,425) based
  178. system and are using GPIO lines for an I2C bus.
  179. This support is also available as a module. If so, the module
  180. will be called i2c-ixp4xx.
  181. config I2C_IXP2000
  182. tristate "IXP2000 GPIO-Based I2C Interface"
  183. depends on I2C && ARCH_IXP2000
  184. select I2C_ALGOBIT
  185. help
  186. Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
  187. system and are using GPIO lines for an I2C bus.
  188. This support is also available as a module. If so, the module
  189. will be called i2c-ixp2000.
  190. config I2C_KEYWEST
  191. tristate "Powermac Keywest I2C interface"
  192. depends on I2C && PPC_PMAC
  193. help
  194. This supports the use of the I2C interface in the combo-I/O
  195. chip on recent Apple machines. Say Y if you have such a machine.
  196. This support is also available as a module. If so, the module
  197. will be called i2c-keywest.
  198. config I2C_MPC
  199. tristate "MPC107/824x/85xx/52xx"
  200. depends on I2C && PPC32
  201. help
  202. If you say yes to this option, support will be included for the
  203. built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
  204. MPC85xx family processors. The driver may also work on 52xx
  205. family processors, though interrupts are known not to work.
  206. This driver can also be built as a module. If so, the module
  207. will be called i2c-mpc.
  208. config I2C_NFORCE2
  209. tristate "Nvidia nForce2, nForce3 and nForce4"
  210. depends on I2C && PCI
  211. help
  212. If you say yes to this option, support will be included for the Nvidia
  213. nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
  214. This driver can also be built as a module. If so, the module
  215. will be called i2c-nforce2.
  216. config I2C_PARPORT
  217. tristate "Parallel port adapter"
  218. depends on I2C && PARPORT
  219. select I2C_ALGOBIT
  220. help
  221. This supports parallel port I2C adapters such as the ones made by
  222. Philips or Velleman, Analog Devices evaluation boards, and more.
  223. Basically any adapter using the parallel port as an I2C bus with
  224. no extra chipset is supported by this driver, or could be.
  225. This driver is a replacement for (and was inspired by) an older
  226. driver named i2c-philips-par. The new driver supports more devices,
  227. and makes it easier to add support for new devices.
  228. Another driver exists, named i2c-parport-light, which doesn't depend
  229. on the parport driver. This is meant for embedded systems. Don't say
  230. Y here if you intend to say Y or M there.
  231. This support is also available as a module. If so, the module
  232. will be called i2c-parport.
  233. config I2C_PARPORT_LIGHT
  234. tristate "Parallel port adapter (light)"
  235. depends on I2C
  236. select I2C_ALGOBIT
  237. help
  238. This supports parallel port I2C adapters such as the ones made by
  239. Philips or Velleman, Analog Devices evaluation boards, and more.
  240. Basically any adapter using the parallel port as an I2C bus with
  241. no extra chipset is supported by this driver, or could be.
  242. This driver is a light version of i2c-parport. It doesn't depend
  243. on the parport driver, and uses direct I/O access instead. This
  244. might be prefered on embedded systems where wasting memory for
  245. the clean but heavy parport handling is not an option. The
  246. drawback is a reduced portability and the impossibility to
  247. dasiy-chain other parallel port devices.
  248. Don't say Y here if you said Y or M to i2c-parport. Saying M to
  249. both is possible but both modules should not be loaded at the same
  250. time.
  251. This support is also available as a module. If so, the module
  252. will be called i2c-parport-light.
  253. config I2C_PROSAVAGE
  254. tristate "S3/VIA (Pro)Savage"
  255. depends on I2C && PCI
  256. select I2C_ALGOBIT
  257. help
  258. If you say yes to this option, support will be included for the
  259. I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
  260. graphics processors.
  261. chipsets supported:
  262. S3/VIA KM266/VT8375 aka ProSavage8
  263. S3/VIA KM133/VT8365 aka Savage4
  264. This support is also available as a module. If so, the module
  265. will be called i2c-prosavage.
  266. config I2C_RPXLITE
  267. tristate "Embedded Planet RPX Lite/Classic support"
  268. depends on (RPXLITE || RPXCLASSIC) && I2C
  269. select I2C_ALGO8XX
  270. config I2C_S3C2410
  271. tristate "S3C2410 I2C Driver"
  272. depends on I2C && ARCH_S3C2410
  273. help
  274. Say Y here to include support for I2C controller in the
  275. Samsung S3C2410 based System-on-Chip devices.
  276. config I2C_SAVAGE4
  277. tristate "S3 Savage 4"
  278. depends on I2C && PCI && EXPERIMENTAL
  279. select I2C_ALGOBIT
  280. help
  281. If you say yes to this option, support will be included for the
  282. S3 Savage 4 I2C interface.
  283. This driver can also be built as a module. If so, the module
  284. will be called i2c-savage4.
  285. config I2C_SIBYTE
  286. tristate "SiByte SMBus interface"
  287. depends on SIBYTE_SB1xxx_SOC && I2C
  288. help
  289. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  290. config SCx200_I2C
  291. tristate "NatSemi SCx200 I2C using GPIO pins"
  292. depends on SCx200_GPIO && I2C
  293. select I2C_ALGOBIT
  294. help
  295. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  296. If you don't know what to do here, say N.
  297. This support is also available as a module. If so, the module
  298. will be called scx200_i2c.
  299. config SCx200_I2C_SCL
  300. int "GPIO pin used for SCL"
  301. depends on SCx200_I2C
  302. default "12"
  303. help
  304. Enter the GPIO pin number used for the SCL signal. This value can
  305. also be specified with a module parameter.
  306. config SCx200_I2C_SDA
  307. int "GPIO pin used for SDA"
  308. depends on SCx200_I2C
  309. default "13"
  310. help
  311. Enter the GPIO pin number used for the SSA signal. This value can
  312. also be specified with a module parameter.
  313. config SCx200_ACB
  314. tristate "NatSemi SCx200 ACCESS.bus"
  315. depends on I2C && PCI
  316. help
  317. Enable the use of the ACCESS.bus controllers of a SCx200 processor.
  318. If you don't know what to do here, say N.
  319. This support is also available as a module. If so, the module
  320. will be called scx200_acb.
  321. config I2C_SIS5595
  322. tristate "SiS 5595"
  323. depends on I2C && PCI
  324. help
  325. If you say yes to this option, support will be included for the
  326. SiS5595 SMBus (a subset of I2C) interface.
  327. This driver can also be built as a module. If so, the module
  328. will be called i2c-sis5595.
  329. config I2C_SIS630
  330. tristate "SiS 630/730"
  331. depends on I2C && PCI
  332. help
  333. If you say yes to this option, support will be included for the
  334. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  335. This driver can also be built as a module. If so, the module
  336. will be called i2c-sis630.
  337. config I2C_SIS96X
  338. tristate "SiS 96x"
  339. depends on I2C && PCI
  340. help
  341. If you say yes to this option, support will be included for the SiS
  342. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  343. chipsets are supported:
  344. 645/961
  345. 645DX/961
  346. 645DX/962
  347. 648/961
  348. 650/961
  349. 735
  350. 745
  351. This driver can also be built as a module. If so, the module
  352. will be called i2c-sis96x.
  353. config I2C_STUB
  354. tristate "I2C/SMBus Test Stub"
  355. depends on I2C && EXPERIMENTAL && 'm'
  356. default 'n'
  357. help
  358. This module may be useful to developers of SMBus client drivers,
  359. especially for certain kinds of sensor chips.
  360. If you do build this module, be sure to read the notes and warnings
  361. in <file:Documentation/i2c/i2c-stub>.
  362. If you don't know what to do here, definitely say N.
  363. config I2C_VIA
  364. tristate "VIA 82C586B"
  365. depends on I2C && PCI && EXPERIMENTAL
  366. select I2C_ALGOBIT
  367. help
  368. If you say yes to this option, support will be included for the VIA
  369. 82C586B I2C interface
  370. This driver can also be built as a module. If so, the module
  371. will be called i2c-via.
  372. config I2C_VIAPRO
  373. tristate "VIA 82C596/82C686/823x"
  374. depends on I2C && PCI
  375. help
  376. If you say yes to this option, support will be included for the VIA
  377. 82C596/82C686/823x I2C interfaces. Specifically, the following
  378. chipsets are supported:
  379. 82C596A/B
  380. 82C686A/B
  381. 8231
  382. 8233
  383. 8233A
  384. 8235
  385. 8237
  386. This driver can also be built as a module. If so, the module
  387. will be called i2c-viapro.
  388. config I2C_VOODOO3
  389. tristate "Voodoo 3"
  390. depends on I2C && PCI
  391. select I2C_ALGOBIT
  392. help
  393. If you say yes to this option, support will be included for the
  394. Voodoo 3 I2C interface.
  395. This driver can also be built as a module. If so, the module
  396. will be called i2c-voodoo3.
  397. config I2C_PCA_ISA
  398. tristate "PCA9564 on an ISA bus"
  399. depends on I2C
  400. select I2C_ALGOPCA
  401. help
  402. This driver supports ISA boards using the Philips PCA 9564
  403. Parallel bus to I2C bus controller
  404. This driver can also be built as a module. If so, the module
  405. will be called i2c-pca-isa.
  406. config I2C_MV64XXX
  407. tristate "Marvell mv64xxx I2C Controller"
  408. depends on I2C && MV64X60 && EXPERIMENTAL
  409. help
  410. If you say yes to this option, support will be included for the
  411. built-in I2C interface on the Marvell 64xxx line of host bridges.
  412. This driver can also be built as a module. If so, the module
  413. will be called i2c-mv64xxx.
  414. endmenu