Kconfig 15 KB

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