Kconfig 17 KB

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