Kconfig 19 KB

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