Kconfig 15 KB

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