Kconfig 18 KB

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