Kconfig 17 KB

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