Kconfig 15 KB

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