Kconfig 16 KB

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