Kconfig 15 KB

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