Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567
  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_AT91
  64. tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
  65. depends on I2C && ARCH_AT91 && EXPERIMENTAL
  66. help
  67. This supports the use of the I2C interface on Atmel AT91
  68. processors.
  69. config I2C_AU1550
  70. tristate "Au1550/Au1200 SMBus interface"
  71. depends on I2C && (SOC_AU1550 || SOC_AU1200)
  72. help
  73. If you say yes to this option, support will be included for the
  74. Au1550 and Au1200 SMBus interface.
  75. This driver can also be built as a module. If so, the module
  76. will be called i2c-au1550.
  77. config I2C_ELEKTOR
  78. tristate "Elektor ISA card"
  79. depends on I2C && ISA && BROKEN_ON_SMP
  80. select I2C_ALGOPCF
  81. help
  82. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  83. such an adapter.
  84. This support is also available as a module. If so, the module
  85. will be called i2c-elektor.
  86. config I2C_HYDRA
  87. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  88. depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
  89. select I2C_ALGOBIT
  90. help
  91. This supports the use of the I2C interface in the Apple Hydra Mac
  92. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  93. have such a machine.
  94. This support is also available as a module. If so, the module
  95. will be called i2c-hydra.
  96. config I2C_I801
  97. tristate "Intel 82801 (ICH)"
  98. depends on I2C && PCI
  99. help
  100. If you say yes to this option, support will be included for the Intel
  101. 801 family of mainboard I2C interfaces. Specifically, the following
  102. versions of the chipset are supported:
  103. 82801AA
  104. 82801AB
  105. 82801BA
  106. 82801CA/CAM
  107. 82801DB
  108. 82801EB/ER (ICH5/ICH5R)
  109. 6300ESB
  110. ICH6
  111. ICH7
  112. ESB2
  113. ICH8
  114. ICH9
  115. This driver can also be built as a module. If so, the module
  116. will be called i2c-i801.
  117. config I2C_I810
  118. tristate "Intel 810/815"
  119. depends on I2C && PCI
  120. select I2C_ALGOBIT
  121. help
  122. If you say yes to this option, support will be included for the Intel
  123. 810/815 family of mainboard I2C interfaces. Specifically, the
  124. following versions of the chipset are supported:
  125. i810AA
  126. i810AB
  127. i810E
  128. i815
  129. i845G
  130. This driver can also be built as a module. If so, the module
  131. will be called i2c-i810.
  132. config I2C_PXA
  133. tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
  134. depends on I2C && EXPERIMENTAL && ARCH_PXA
  135. help
  136. If you have devices in the PXA I2C bus, say yes to this option.
  137. This driver can also be built as a module. If so, the module
  138. will be called i2c-pxa.
  139. config I2C_PXA_SLAVE
  140. bool "Intel PXA2XX I2C Slave comms support"
  141. depends on I2C_PXA
  142. help
  143. Support I2C slave mode communications on the PXA I2C bus. This
  144. is necessary for systems where the PXA may be a target on the
  145. I2C bus.
  146. config I2C_PIIX4
  147. tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
  148. depends on I2C && PCI
  149. help
  150. If you say yes to this option, support will be included for the Intel
  151. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  152. versions of the chipset are supported (note that Serverworks is part
  153. of Broadcom):
  154. Intel PIIX4
  155. Intel 440MX
  156. ATI IXP200
  157. ATI IXP300
  158. ATI IXP400
  159. Serverworks OSB4
  160. Serverworks CSB5
  161. Serverworks CSB6
  162. Serverworks HT-1000
  163. SMSC Victory66
  164. This driver can also be built as a module. If so, the module
  165. will be called i2c-piix4.
  166. config I2C_IBM_IIC
  167. tristate "IBM PPC 4xx on-chip I2C interface"
  168. depends on IBM_OCP && I2C
  169. help
  170. Say Y here if you want to use IIC peripheral found on
  171. embedded IBM PPC 4xx based systems.
  172. This driver can also be built as a module. If so, the module
  173. will be called i2c-ibm_iic.
  174. config I2C_IOP3XX
  175. tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
  176. depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX) && I2C
  177. help
  178. Say Y here if you want to use the IIC bus controller on
  179. the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
  180. This driver can also be built as a module. If so, the module
  181. will be called i2c-iop3xx.
  182. config I2C_ISA
  183. tristate
  184. depends on I2C
  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/86xx"
  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/MPC8641 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_OCORES
  232. tristate "OpenCores I2C Controller"
  233. depends on I2C && EXPERIMENTAL
  234. help
  235. If you say yes to this option, support will be included for the
  236. OpenCores I2C controller. For details see
  237. http://www.opencores.org/projects.cgi/web/i2c/overview
  238. This driver can also be built as a module. If so, the module
  239. will be called i2c-ocores.
  240. config I2C_OMAP
  241. tristate "OMAP I2C adapter"
  242. depends on I2C && ARCH_OMAP
  243. default y if MACH_OMAP_H3 || MACH_OMAP_OSK
  244. help
  245. If you say yes to this option, support will be included for the
  246. I2C interface on the Texas Instruments OMAP1/2 family of processors.
  247. Like OMAP1510/1610/1710/5912 and OMAP242x.
  248. For details see http://www.ti.com/omap.
  249. config I2C_PARPORT
  250. tristate "Parallel port adapter"
  251. depends on I2C && PARPORT
  252. select I2C_ALGOBIT
  253. help
  254. This supports parallel port I2C adapters such as the ones made by
  255. Philips or Velleman, Analog Devices evaluation boards, and more.
  256. Basically any adapter using the parallel port as an I2C bus with
  257. no extra chipset is supported by this driver, or could be.
  258. This driver is a replacement for (and was inspired by) an older
  259. driver named i2c-philips-par. The new driver supports more devices,
  260. and makes it easier to add support for new devices.
  261. An adapter type parameter is now mandatory. Please read the file
  262. Documentation/i2c/busses/i2c-parport for details.
  263. Another driver exists, named i2c-parport-light, which doesn't depend
  264. on the parport driver. This is meant for embedded systems. Don't say
  265. Y here if you intend to say Y or M there.
  266. This support is also available as a module. If so, the module
  267. will be called i2c-parport.
  268. config I2C_PARPORT_LIGHT
  269. tristate "Parallel port adapter (light)"
  270. depends on I2C
  271. select I2C_ALGOBIT
  272. help
  273. This supports parallel port I2C adapters such as the ones made by
  274. Philips or Velleman, Analog Devices evaluation boards, and more.
  275. Basically any adapter using the parallel port as an I2C bus with
  276. no extra chipset is supported by this driver, or could be.
  277. This driver is a light version of i2c-parport. It doesn't depend
  278. on the parport driver, and uses direct I/O access instead. This
  279. might be preferred on embedded systems where wasting memory for
  280. the clean but heavy parport handling is not an option. The
  281. drawback is a reduced portability and the impossibility to
  282. daisy-chain other parallel port devices.
  283. Don't say Y here if you said Y or M to i2c-parport. Saying M to
  284. both is possible but both modules should not be loaded at the same
  285. time.
  286. This support is also available as a module. If so, the module
  287. will be called i2c-parport-light.
  288. config I2C_PROSAVAGE
  289. tristate "S3/VIA (Pro)Savage"
  290. depends on I2C && PCI
  291. select I2C_ALGOBIT
  292. help
  293. If you say yes to this option, support will be included for the
  294. I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
  295. graphics processors.
  296. chipsets supported:
  297. S3/VIA KM266/VT8375 aka ProSavage8
  298. S3/VIA KM133/VT8365 aka Savage4
  299. This support is also available as a module. If so, the module
  300. will be called i2c-prosavage.
  301. config I2C_RPXLITE
  302. tristate "Embedded Planet RPX Lite/Classic support"
  303. depends on (RPXLITE || RPXCLASSIC) && I2C
  304. select I2C_ALGO8XX
  305. config I2C_S3C2410
  306. tristate "S3C2410 I2C Driver"
  307. depends on I2C && ARCH_S3C2410
  308. help
  309. Say Y here to include support for I2C controller in the
  310. Samsung S3C2410 based System-on-Chip devices.
  311. config I2C_SAVAGE4
  312. tristate "S3 Savage 4"
  313. depends on I2C && PCI && EXPERIMENTAL
  314. select I2C_ALGOBIT
  315. help
  316. If you say yes to this option, support will be included for the
  317. S3 Savage 4 I2C interface.
  318. This driver can also be built as a module. If so, the module
  319. will be called i2c-savage4.
  320. config I2C_SIBYTE
  321. tristate "SiByte SMBus interface"
  322. depends on SIBYTE_SB1xxx_SOC && I2C
  323. help
  324. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  325. config SCx200_I2C
  326. tristate "NatSemi SCx200 I2C using GPIO pins"
  327. depends on SCx200_GPIO && I2C
  328. select I2C_ALGOBIT
  329. help
  330. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  331. If you don't know what to do here, say N.
  332. This support is also available as a module. If so, the module
  333. will be called scx200_i2c.
  334. config SCx200_I2C_SCL
  335. int "GPIO pin used for SCL"
  336. depends on SCx200_I2C
  337. default "12"
  338. help
  339. Enter the GPIO pin number used for the SCL signal. This value can
  340. also be specified with a module parameter.
  341. config SCx200_I2C_SDA
  342. int "GPIO pin used for SDA"
  343. depends on SCx200_I2C
  344. default "13"
  345. help
  346. Enter the GPIO pin number used for the SSA signal. This value can
  347. also be specified with a module parameter.
  348. config SCx200_ACB
  349. tristate "Geode ACCESS.bus support"
  350. depends on X86_32 && I2C && PCI
  351. help
  352. Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
  353. SC1100 processors and the CS5535 and CS5536 Geode companion devices.
  354. If you don't know what to do here, say N.
  355. This support is also available as a module. If so, the module
  356. will be called scx200_acb.
  357. config I2C_SIS5595
  358. tristate "SiS 5595"
  359. depends on I2C && PCI
  360. help
  361. If you say yes to this option, support will be included for the
  362. SiS5595 SMBus (a subset of I2C) interface.
  363. This driver can also be built as a module. If so, the module
  364. will be called i2c-sis5595.
  365. config I2C_SIS630
  366. tristate "SiS 630/730"
  367. depends on I2C && PCI
  368. help
  369. If you say yes to this option, support will be included for the
  370. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  371. This driver can also be built as a module. If so, the module
  372. will be called i2c-sis630.
  373. config I2C_SIS96X
  374. tristate "SiS 96x"
  375. depends on I2C && PCI
  376. help
  377. If you say yes to this option, support will be included for the SiS
  378. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  379. chipsets are supported:
  380. 645/961
  381. 645DX/961
  382. 645DX/962
  383. 648/961
  384. 650/961
  385. 735
  386. 745
  387. This driver can also be built as a module. If so, the module
  388. will be called i2c-sis96x.
  389. config I2C_STUB
  390. tristate "I2C/SMBus Test Stub"
  391. depends on I2C && EXPERIMENTAL && 'm'
  392. default 'n'
  393. help
  394. This module may be useful to developers of SMBus client drivers,
  395. especially for certain kinds of sensor chips.
  396. If you do build this module, be sure to read the notes and warnings
  397. in <file:Documentation/i2c/i2c-stub>.
  398. If you don't know what to do here, definitely say N.
  399. config I2C_VERSATILE
  400. tristate "ARM Versatile/Realview I2C bus support"
  401. depends on I2C && (ARCH_VERSATILE || ARCH_REALVIEW)
  402. select I2C_ALGOBIT
  403. help
  404. Say yes if you want to support the I2C serial bus on ARMs Versatile
  405. range of platforms.
  406. This driver can also be built as a module. If so, the module
  407. will be called i2c-versatile.
  408. config I2C_VIA
  409. tristate "VIA 82C586B"
  410. depends on I2C && PCI && EXPERIMENTAL
  411. select I2C_ALGOBIT
  412. help
  413. If you say yes to this option, support will be included for the VIA
  414. 82C586B I2C interface
  415. This driver can also be built as a module. If so, the module
  416. will be called i2c-via.
  417. config I2C_VIAPRO
  418. tristate "VIA 82C596/82C686/82xx"
  419. depends on I2C && PCI
  420. help
  421. If you say yes to this option, support will be included for the VIA
  422. 82C596/82C686/82xx I2C interfaces. Specifically, the following
  423. chipsets are supported:
  424. VT82C596A/B
  425. VT82C686A/B
  426. VT8231
  427. VT8233/A
  428. VT8235
  429. VT8237R/A
  430. VT8251
  431. This driver can also be built as a module. If so, the module
  432. will be called i2c-viapro.
  433. config I2C_VOODOO3
  434. tristate "Voodoo 3"
  435. depends on I2C && PCI
  436. select I2C_ALGOBIT
  437. help
  438. If you say yes to this option, support will be included for the
  439. Voodoo 3 I2C interface.
  440. This driver can also be built as a module. If so, the module
  441. will be called i2c-voodoo3.
  442. config I2C_PCA_ISA
  443. tristate "PCA9564 on an ISA bus"
  444. depends on I2C
  445. select I2C_ALGOPCA
  446. default n
  447. help
  448. This driver supports ISA boards using the Philips PCA 9564
  449. Parallel bus to I2C bus controller
  450. This driver can also be built as a module. If so, the module
  451. will be called i2c-pca-isa.
  452. This device is almost undetectable and using this driver on a
  453. system which doesn't have this device will result in long
  454. delays when I2C/SMBus chip drivers are loaded (e.g. at boot
  455. time). If unsure, say N.
  456. config I2C_MV64XXX
  457. tristate "Marvell mv64xxx I2C Controller"
  458. depends on I2C && MV64X60 && EXPERIMENTAL
  459. help
  460. If you say yes to this option, support will be included for the
  461. built-in I2C interface on the Marvell 64xxx line of host bridges.
  462. This driver can also be built as a module. If so, the module
  463. will be called i2c-mv64xxx.
  464. config I2C_PNX
  465. tristate "I2C bus support for Philips PNX targets"
  466. depends on ARCH_PNX4008 && I2C
  467. help
  468. This driver supports the Philips IP3204 I2C IP block master and/or
  469. slave controller
  470. This driver can also be built as a module. If so, the module
  471. will be called i2c-pnx.
  472. endmenu