Kconfig 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901
  1. #
  2. # Sensor device configuration
  3. #
  4. menu "I2C Hardware Bus support"
  5. comment "PC SMBus host controller drivers"
  6. depends on PCI
  7. config I2C_ALI1535
  8. tristate "ALI 1535"
  9. depends on PCI
  10. help
  11. If you say yes to this option, support will be included for the SMB
  12. Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
  13. controller is part of the 7101 device, which is an ACPI-compliant
  14. Power Management Unit (PMU).
  15. This driver can also be built as a module. If so, the module
  16. will be called i2c-ali1535.
  17. config I2C_ALI1563
  18. tristate "ALI 1563"
  19. depends on PCI && EXPERIMENTAL
  20. help
  21. If you say yes to this option, support will be included for the SMB
  22. Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
  23. controller is part of the 7101 device, which is an ACPI-compliant
  24. Power Management Unit (PMU).
  25. This driver can also be built as a module. If so, the module
  26. will be called i2c-ali1563.
  27. config I2C_ALI15X3
  28. tristate "ALI 15x3"
  29. depends on PCI
  30. help
  31. If you say yes to this option, support will be included for the
  32. Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
  33. This driver can also be built as a module. If so, the module
  34. will be called i2c-ali15x3.
  35. config I2C_AMD756
  36. tristate "AMD 756/766/768/8111 and nVidia nForce"
  37. depends on PCI
  38. help
  39. If you say yes to this option, support will be included for the AMD
  40. 756/766/768 mainboard I2C interfaces. The driver also includes
  41. support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
  42. the nVidia nForce I2C interface.
  43. This driver can also be built as a module. If so, the module
  44. will be called i2c-amd756.
  45. config I2C_AMD756_S4882
  46. tristate "SMBus multiplexing on the Tyan S4882"
  47. depends on I2C_AMD756 && X86 && EXPERIMENTAL
  48. help
  49. Enabling this option will add specific SMBus support for the Tyan
  50. S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
  51. over 8 different channels, where the various memory module EEPROMs
  52. and temperature sensors live. Saying yes here will give you access
  53. to these in addition to the trunk.
  54. This driver can also be built as a module. If so, the module
  55. will be called i2c-amd756-s4882.
  56. config I2C_AMD8111
  57. tristate "AMD 8111"
  58. depends on PCI
  59. help
  60. If you say yes to this option, support will be included for the
  61. second (SMBus 2.0) AMD 8111 mainboard I2C interface.
  62. This driver can also be built as a module. If so, the module
  63. will be called i2c-amd8111.
  64. config I2C_I801
  65. tristate "Intel 82801 (ICH/PCH)"
  66. depends on PCI
  67. select CHECK_SIGNATURE if X86 && DMI
  68. help
  69. If you say yes to this option, support will be included for the Intel
  70. 801 family of mainboard I2C interfaces. Specifically, the following
  71. versions of the chipset are supported:
  72. 82801AA
  73. 82801AB
  74. 82801BA
  75. 82801CA/CAM
  76. 82801DB
  77. 82801EB/ER (ICH5/ICH5R)
  78. 6300ESB
  79. ICH6
  80. ICH7
  81. ESB2
  82. ICH8
  83. ICH9
  84. EP80579 (Tolapai)
  85. ICH10
  86. 5/3400 Series (PCH)
  87. 6 Series (PCH)
  88. Patsburg (PCH)
  89. DH89xxCC (PCH)
  90. Panther Point (PCH)
  91. Lynx Point (PCH)
  92. This driver can also be built as a module. If so, the module
  93. will be called i2c-i801.
  94. config I2C_ISCH
  95. tristate "Intel SCH SMBus 1.0"
  96. depends on PCI
  97. select LPC_SCH
  98. help
  99. Say Y here if you want to use SMBus controller on the Intel SCH
  100. based systems.
  101. This driver can also be built as a module. If so, the module
  102. will be called i2c-isch.
  103. config I2C_PIIX4
  104. tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
  105. depends on PCI
  106. help
  107. If you say yes to this option, support will be included for the Intel
  108. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  109. versions of the chipset are supported (note that Serverworks is part
  110. of Broadcom):
  111. Intel PIIX4
  112. Intel 440MX
  113. ATI IXP200
  114. ATI IXP300
  115. ATI IXP400
  116. ATI SB600
  117. ATI SB700/SP5100
  118. ATI SB800
  119. AMD Hudson-2
  120. Serverworks OSB4
  121. Serverworks CSB5
  122. Serverworks CSB6
  123. Serverworks HT-1000
  124. Serverworks HT-1100
  125. SMSC Victory66
  126. Some AMD chipsets contain two PIIX4-compatible SMBus
  127. controllers. This driver will attempt to use both controllers
  128. on the SB700/SP5100, if they have been initialized by the BIOS.
  129. This driver can also be built as a module. If so, the module
  130. will be called i2c-piix4.
  131. config I2C_NFORCE2
  132. tristate "Nvidia nForce2, nForce3 and nForce4"
  133. depends on PCI
  134. help
  135. If you say yes to this option, support will be included for the Nvidia
  136. nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
  137. This driver can also be built as a module. If so, the module
  138. will be called i2c-nforce2.
  139. config I2C_NFORCE2_S4985
  140. tristate "SMBus multiplexing on the Tyan S4985"
  141. depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
  142. help
  143. Enabling this option will add specific SMBus support for the Tyan
  144. S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
  145. over 4 different channels, where the various memory module EEPROMs
  146. live. Saying yes here will give you access to these in addition
  147. to the trunk.
  148. This driver can also be built as a module. If so, the module
  149. will be called i2c-nforce2-s4985.
  150. config I2C_SIS5595
  151. tristate "SiS 5595"
  152. depends on PCI
  153. help
  154. If you say yes to this option, support will be included for the
  155. SiS5595 SMBus (a subset of I2C) interface.
  156. This driver can also be built as a module. If so, the module
  157. will be called i2c-sis5595.
  158. config I2C_SIS630
  159. tristate "SiS 630/730"
  160. depends on PCI
  161. help
  162. If you say yes to this option, support will be included for the
  163. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  164. This driver can also be built as a module. If so, the module
  165. will be called i2c-sis630.
  166. config I2C_SIS96X
  167. tristate "SiS 96x"
  168. depends on PCI
  169. help
  170. If you say yes to this option, support will be included for the SiS
  171. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  172. chipsets are supported:
  173. 645/961
  174. 645DX/961
  175. 645DX/962
  176. 648/961
  177. 650/961
  178. 735
  179. 745
  180. This driver can also be built as a module. If so, the module
  181. will be called i2c-sis96x.
  182. config I2C_VIA
  183. tristate "VIA VT82C586B"
  184. depends on PCI && EXPERIMENTAL
  185. select I2C_ALGOBIT
  186. help
  187. If you say yes to this option, support will be included for the VIA
  188. 82C586B I2C interface
  189. This driver can also be built as a module. If so, the module
  190. will be called i2c-via.
  191. config I2C_VIAPRO
  192. tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
  193. depends on PCI
  194. help
  195. If you say yes to this option, support will be included for the VIA
  196. VT82C596 and later SMBus interface. Specifically, the following
  197. chipsets are supported:
  198. VT82C596A/B
  199. VT82C686A/B
  200. VT8231
  201. VT8233/A
  202. VT8235
  203. VT8237R/A/S
  204. VT8251
  205. CX700
  206. VX800/VX820
  207. VX855/VX875
  208. This driver can also be built as a module. If so, the module
  209. will be called i2c-viapro.
  210. if ACPI
  211. comment "ACPI drivers"
  212. config I2C_SCMI
  213. tristate "SMBus Control Method Interface"
  214. help
  215. This driver supports the SMBus Control Method Interface. It needs the
  216. BIOS to declare ACPI control methods as described in the SMBus Control
  217. Method Interface specification.
  218. To compile this driver as a module, choose M here:
  219. the module will be called i2c-scmi.
  220. endif # ACPI
  221. comment "Mac SMBus host controller drivers"
  222. depends on PPC_CHRP || PPC_PMAC
  223. config I2C_HYDRA
  224. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  225. depends on PCI && PPC_CHRP && EXPERIMENTAL
  226. select I2C_ALGOBIT
  227. help
  228. This supports the use of the I2C interface in the Apple Hydra Mac
  229. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  230. have such a machine.
  231. This support is also available as a module. If so, the module
  232. will be called i2c-hydra.
  233. config I2C_POWERMAC
  234. tristate "Powermac I2C interface"
  235. depends on PPC_PMAC
  236. default y
  237. help
  238. This exposes the various PowerMac i2c interfaces to the linux i2c
  239. layer and to userland. It is used by various drivers on the PowerMac
  240. platform, and should generally be enabled.
  241. This support is also available as a module. If so, the module
  242. will be called i2c-powermac.
  243. comment "I2C system bus drivers (mostly embedded / system-on-chip)"
  244. config I2C_AT91
  245. tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
  246. depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
  247. help
  248. This supports the use of the I2C interface on Atmel AT91
  249. processors.
  250. This driver is BROKEN because the controller which it uses
  251. will easily trigger RX overrun and TX underrun errors. Using
  252. low I2C clock rates may partially work around those issues
  253. on some systems. Another serious problem is that there is no
  254. documented way to issue repeated START conditions, as needed
  255. to support combined I2C messages. Use the i2c-gpio driver
  256. unless your system can cope with those limitations.
  257. config I2C_AU1550
  258. tristate "Au1550/Au1200/Au1300 SMBus interface"
  259. depends on MIPS_ALCHEMY
  260. help
  261. If you say yes to this option, support will be included for the
  262. Au1550/Au1200/Au1300 SMBus interface.
  263. This driver can also be built as a module. If so, the module
  264. will be called i2c-au1550.
  265. config I2C_BLACKFIN_TWI
  266. tristate "Blackfin TWI I2C support"
  267. depends on BLACKFIN
  268. depends on !BF561 && !BF531 && !BF532 && !BF533
  269. help
  270. This is the I2C bus driver for Blackfin on-chip TWI interface.
  271. This driver can also be built as a module. If so, the module
  272. will be called i2c-bfin-twi.
  273. config I2C_BLACKFIN_TWI_CLK_KHZ
  274. int "Blackfin TWI I2C clock (kHz)"
  275. depends on I2C_BLACKFIN_TWI
  276. range 21 400
  277. default 50
  278. help
  279. The unit of the TWI clock is kHz.
  280. config I2C_CPM
  281. tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
  282. depends on (CPM1 || CPM2) && OF_I2C
  283. help
  284. This supports the use of the I2C interface on Freescale
  285. processors with CPM1 or CPM2.
  286. This driver can also be built as a module. If so, the module
  287. will be called i2c-cpm.
  288. config I2C_DAVINCI
  289. tristate "DaVinci I2C driver"
  290. depends on ARCH_DAVINCI
  291. help
  292. Support for TI DaVinci I2C controller driver.
  293. This driver can also be built as a module. If so, the module
  294. will be called i2c-davinci.
  295. Please note that this driver might be needed to bring up other
  296. devices such as DaVinci NIC.
  297. For details please see http://www.ti.com/davinci
  298. config I2C_DESIGNWARE_PLATFORM
  299. tristate "Synopsys DesignWare Platform"
  300. depends on HAVE_CLK
  301. help
  302. If you say yes to this option, support will be included for the
  303. Synopsys DesignWare I2C adapter. Only master mode is supported.
  304. This driver can also be built as a module. If so, the module
  305. will be called i2c-designware-platform.
  306. config I2C_DESIGNWARE_PCI
  307. tristate "Synopsys DesignWare PCI"
  308. depends on PCI
  309. help
  310. If you say yes to this option, support will be included for the
  311. Synopsys DesignWare I2C adapter. Only master mode is supported.
  312. This driver can also be built as a module. If so, the module
  313. will be called i2c-designware-pci.
  314. config I2C_EG20T
  315. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
  316. depends on PCI
  317. help
  318. This driver is for PCH(Platform controller Hub) I2C of EG20T which
  319. is an IOH(Input/Output Hub) for x86 embedded processor.
  320. This driver can access PCH I2C bus device.
  321. This driver also can be used for LAPIS Semiconductor IOH(Input/
  322. Output Hub), ML7213, ML7223 and ML7831.
  323. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  324. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  325. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  326. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  327. config I2C_GPIO
  328. tristate "GPIO-based bitbanging I2C"
  329. depends on GENERIC_GPIO
  330. select I2C_ALGOBIT
  331. help
  332. This is a very simple bitbanging I2C driver utilizing the
  333. arch-neutral GPIO API to control the SCL and SDA lines.
  334. config I2C_HIGHLANDER
  335. tristate "Highlander FPGA SMBus interface"
  336. depends on SH_HIGHLANDER
  337. help
  338. If you say yes to this option, support will be included for
  339. the SMBus interface located in the FPGA on various Highlander
  340. boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
  341. FPGAs. This is wholly unrelated to the SoC I2C.
  342. This driver can also be built as a module. If so, the module
  343. will be called i2c-highlander.
  344. config I2C_IBM_IIC
  345. tristate "IBM PPC 4xx on-chip I2C interface"
  346. depends on 4xx
  347. help
  348. Say Y here if you want to use IIC peripheral found on
  349. embedded IBM PPC 4xx based systems.
  350. This driver can also be built as a module. If so, the module
  351. will be called i2c-ibm_iic.
  352. config I2C_IMX
  353. tristate "IMX I2C interface"
  354. depends on ARCH_MXC
  355. help
  356. Say Y here if you want to use the IIC bus controller on
  357. the Freescale i.MX/MXC processors.
  358. This driver can also be built as a module. If so, the module
  359. will be called i2c-imx.
  360. config I2C_INTEL_MID
  361. tristate "Intel Moorestown/Medfield Platform I2C controller"
  362. depends on PCI
  363. help
  364. Say Y here if you have an Intel Moorestown/Medfield platform I2C
  365. controller.
  366. This support is also available as a module. If so, the module
  367. will be called i2c-intel-mid.
  368. config I2C_IOP3XX
  369. tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
  370. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
  371. help
  372. Say Y here if you want to use the IIC bus controller on
  373. the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
  374. This driver can also be built as a module. If so, the module
  375. will be called i2c-iop3xx.
  376. config I2C_MPC
  377. tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
  378. depends on PPC
  379. help
  380. If you say yes to this option, support will be included for the
  381. built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
  382. MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
  383. This driver can also be built as a module. If so, the module
  384. will be called i2c-mpc.
  385. config I2C_MV64XXX
  386. tristate "Marvell mv64xxx I2C Controller"
  387. depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
  388. help
  389. If you say yes to this option, support will be included for the
  390. built-in I2C interface on the Marvell 64xxx line of host bridges.
  391. This driver can also be built as a module. If so, the module
  392. will be called i2c-mv64xxx.
  393. config I2C_MXS
  394. tristate "Freescale i.MX28 I2C interface"
  395. depends on SOC_IMX28
  396. select STMP_DEVICE
  397. help
  398. Say Y here if you want to use the I2C bus controller on
  399. the Freescale i.MX28 processors.
  400. This driver can also be built as a module. If so, the module
  401. will be called i2c-mxs.
  402. config I2C_NOMADIK
  403. tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
  404. depends on PLAT_NOMADIK
  405. help
  406. If you say yes to this option, support will be included for the
  407. I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
  408. config I2C_NUC900
  409. tristate "NUC900 I2C Driver"
  410. depends on ARCH_W90X900
  411. help
  412. Say Y here to include support for I2C controller in the
  413. Winbond/Nuvoton NUC900 based System-on-Chip devices.
  414. config I2C_OCORES
  415. tristate "OpenCores I2C Controller"
  416. depends on EXPERIMENTAL
  417. help
  418. If you say yes to this option, support will be included for the
  419. OpenCores I2C controller. For details see
  420. http://www.opencores.org/projects.cgi/web/i2c/overview
  421. This driver can also be built as a module. If so, the module
  422. will be called i2c-ocores.
  423. config I2C_OMAP
  424. tristate "OMAP I2C adapter"
  425. depends on ARCH_OMAP
  426. default y if MACH_OMAP_H3 || MACH_OMAP_OSK
  427. help
  428. If you say yes to this option, support will be included for the
  429. I2C interface on the Texas Instruments OMAP1/2 family of processors.
  430. Like OMAP1510/1610/1710/5912 and OMAP242x.
  431. For details see http://www.ti.com/omap.
  432. config I2C_PASEMI
  433. tristate "PA Semi SMBus interface"
  434. depends on PPC_PASEMI && PCI
  435. help
  436. Supports the PA Semi PWRficient on-chip SMBus interfaces.
  437. config I2C_PCA_PLATFORM
  438. tristate "PCA9564/PCA9665 as platform device"
  439. select I2C_ALGOPCA
  440. default n
  441. help
  442. This driver supports a memory mapped Philips PCA9564/PCA9665
  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-platform.
  446. config I2C_PMCMSP
  447. tristate "PMC MSP I2C TWI Controller"
  448. depends on PMC_MSP
  449. help
  450. This driver supports the PMC TWI controller on MSP devices.
  451. This driver can also be built as module. If so, the module
  452. will be called i2c-pmcmsp.
  453. config I2C_PNX
  454. tristate "I2C bus support for Philips PNX and NXP LPC targets"
  455. depends on ARCH_PNX4008 || ARCH_LPC32XX
  456. help
  457. This driver supports the Philips IP3204 I2C IP block master and/or
  458. slave controller
  459. This driver can also be built as a module. If so, the module
  460. will be called i2c-pnx.
  461. config I2C_PUV3
  462. tristate "PKUnity v3 I2C bus support"
  463. depends on UNICORE32 && ARCH_PUV3
  464. select I2C_ALGOBIT
  465. help
  466. This driver supports the I2C IP inside the PKUnity-v3 SoC.
  467. This I2C bus controller is under AMBA/AXI bus.
  468. This driver can also be built as a module. If so, the module
  469. will be called i2c-puv3.
  470. config I2C_PXA
  471. tristate "Intel PXA2XX I2C adapter"
  472. depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
  473. help
  474. If you have devices in the PXA I2C bus, say yes to this option.
  475. This driver can also be built as a module. If so, the module
  476. will be called i2c-pxa.
  477. config I2C_PXA_PCI
  478. def_bool I2C_PXA && X86_32 && PCI && OF
  479. config I2C_PXA_SLAVE
  480. bool "Intel PXA2XX I2C Slave comms support"
  481. depends on I2C_PXA && !X86_32
  482. help
  483. Support I2C slave mode communications on the PXA I2C bus. This
  484. is necessary for systems where the PXA may be a target on the
  485. I2C bus.
  486. config HAVE_S3C2410_I2C
  487. bool
  488. help
  489. This will include I2C support for Samsung SoCs. If you want to
  490. include I2C support for any machine, kindly select this in the
  491. respective Kconfig file.
  492. config I2C_S3C2410
  493. tristate "S3C2410 I2C Driver"
  494. depends on HAVE_S3C2410_I2C
  495. help
  496. Say Y here to include support for I2C controller in the
  497. Samsung SoCs.
  498. config I2C_S6000
  499. tristate "S6000 I2C support"
  500. depends on XTENSA_VARIANT_S6000
  501. help
  502. This driver supports the on chip I2C device on the
  503. S6000 xtensa processor family.
  504. To compile this driver as a module, choose M here. The module
  505. will be called i2c-s6000.
  506. config I2C_SH7760
  507. tristate "Renesas SH7760 I2C Controller"
  508. depends on CPU_SUBTYPE_SH7760
  509. help
  510. This driver supports the 2 I2C interfaces on the Renesas SH7760.
  511. This driver can also be built as a module. If so, the module
  512. will be called i2c-sh7760.
  513. config I2C_SH_MOBILE
  514. tristate "SuperH Mobile I2C Controller"
  515. depends on SUPERH || ARCH_SHMOBILE
  516. help
  517. If you say yes to this option, support will be included for the
  518. built-in I2C interface on the Renesas SH-Mobile processor.
  519. This driver can also be built as a module. If so, the module
  520. will be called i2c-sh_mobile.
  521. config I2C_SIMTEC
  522. tristate "Simtec Generic I2C interface"
  523. select I2C_ALGOBIT
  524. help
  525. If you say yes to this option, support will be included for
  526. the Simtec Generic I2C interface. This driver is for the
  527. simple I2C bus used on newer Simtec products for general
  528. I2C, such as DDC on the Simtec BBD2016A.
  529. This driver can also be built as a module. If so, the module
  530. will be called i2c-simtec.
  531. config I2C_SIRF
  532. tristate "CSR SiRFprimaII I2C interface"
  533. depends on ARCH_PRIMA2
  534. help
  535. If you say yes to this option, support will be included for the
  536. CSR SiRFprimaII I2C interface.
  537. This driver can also be built as a module. If so, the module
  538. will be called i2c-sirf.
  539. config I2C_STU300
  540. tristate "ST Microelectronics DDC I2C interface"
  541. depends on MACH_U300
  542. default y if MACH_U300
  543. help
  544. If you say yes to this option, support will be included for the
  545. I2C interface from ST Microelectronics simply called "DDC I2C"
  546. supporting both I2C and DDC, used in e.g. the U300 series
  547. mobile platforms.
  548. This driver can also be built as a module. If so, the module
  549. will be called i2c-stu300.
  550. config I2C_TEGRA
  551. tristate "NVIDIA Tegra internal I2C controller"
  552. depends on ARCH_TEGRA
  553. help
  554. If you say yes to this option, support will be included for the
  555. I2C controller embedded in NVIDIA Tegra SOCs
  556. config I2C_VERSATILE
  557. tristate "ARM Versatile/Realview I2C bus support"
  558. depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
  559. select I2C_ALGOBIT
  560. help
  561. Say yes if you want to support the I2C serial bus on ARMs Versatile
  562. range of platforms.
  563. This driver can also be built as a module. If so, the module
  564. will be called i2c-versatile.
  565. config I2C_OCTEON
  566. tristate "Cavium OCTEON I2C bus support"
  567. depends on CPU_CAVIUM_OCTEON
  568. help
  569. Say yes if you want to support the I2C serial bus on Cavium
  570. OCTEON SOC.
  571. This driver can also be built as a module. If so, the module
  572. will be called i2c-octeon.
  573. config I2C_XILINX
  574. tristate "Xilinx I2C Controller"
  575. depends on EXPERIMENTAL && HAS_IOMEM
  576. help
  577. If you say yes to this option, support will be included for the
  578. Xilinx I2C controller.
  579. This driver can also be built as a module. If so, the module
  580. will be called xilinx_i2c.
  581. config I2C_XLR
  582. tristate "XLR I2C support"
  583. depends on CPU_XLR
  584. help
  585. This driver enables support for the on-chip I2C interface of
  586. the Netlogic XLR/XLS MIPS processors.
  587. This driver can also be built as a module. If so, the module
  588. will be called i2c-xlr.
  589. comment "External I2C/SMBus adapter drivers"
  590. config I2C_DIOLAN_U2C
  591. tristate "Diolan U2C-12 USB adapter"
  592. depends on USB
  593. help
  594. If you say yes to this option, support will be included for Diolan
  595. U2C-12, a USB to I2C interface.
  596. This driver can also be built as a module. If so, the module
  597. will be called i2c-diolan-u2c.
  598. config I2C_PARPORT
  599. tristate "Parallel port adapter"
  600. depends on PARPORT
  601. select I2C_ALGOBIT
  602. select I2C_SMBUS
  603. help
  604. This supports parallel port I2C adapters such as the ones made by
  605. Philips or Velleman, Analog Devices evaluation boards, and more.
  606. Basically any adapter using the parallel port as an I2C bus with
  607. no extra chipset is supported by this driver, or could be.
  608. This driver is a replacement for (and was inspired by) an older
  609. driver named i2c-philips-par. The new driver supports more devices,
  610. and makes it easier to add support for new devices.
  611. An adapter type parameter is now mandatory. Please read the file
  612. Documentation/i2c/busses/i2c-parport for details.
  613. Another driver exists, named i2c-parport-light, which doesn't depend
  614. on the parport driver. This is meant for embedded systems. Don't say
  615. Y here if you intend to say Y or M there.
  616. This support is also available as a module. If so, the module
  617. will be called i2c-parport.
  618. config I2C_PARPORT_LIGHT
  619. tristate "Parallel port adapter (light)"
  620. select I2C_ALGOBIT
  621. select I2C_SMBUS
  622. help
  623. This supports parallel port I2C adapters such as the ones made by
  624. Philips or Velleman, Analog Devices evaluation boards, and more.
  625. Basically any adapter using the parallel port as an I2C bus with
  626. no extra chipset is supported by this driver, or could be.
  627. This driver is a light version of i2c-parport. It doesn't depend
  628. on the parport driver, and uses direct I/O access instead. This
  629. might be preferred on embedded systems where wasting memory for
  630. the clean but heavy parport handling is not an option. The
  631. drawback is a reduced portability and the impossibility to
  632. daisy-chain other parallel port devices.
  633. Don't say Y here if you said Y or M to i2c-parport. Saying M to
  634. both is possible but both modules should not be loaded at the same
  635. time.
  636. This support is also available as a module. If so, the module
  637. will be called i2c-parport-light.
  638. config I2C_TAOS_EVM
  639. tristate "TAOS evaluation module"
  640. depends on EXPERIMENTAL
  641. select SERIO
  642. select SERIO_SERPORT
  643. default n
  644. help
  645. This supports TAOS evaluation modules on serial port. In order to
  646. use this driver, you will need the inputattach tool, which is part
  647. of the input-utils package.
  648. If unsure, say N.
  649. This support is also available as a module. If so, the module
  650. will be called i2c-taos-evm.
  651. config I2C_TINY_USB
  652. tristate "Tiny-USB adapter"
  653. depends on USB
  654. help
  655. If you say yes to this option, support will be included for the
  656. i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
  657. http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
  658. This driver can also be built as a module. If so, the module
  659. will be called i2c-tiny-usb.
  660. comment "Other I2C/SMBus bus drivers"
  661. config I2C_ACORN
  662. tristate "Acorn IOC/IOMD I2C bus support"
  663. depends on ARCH_ACORN
  664. default y
  665. select I2C_ALGOBIT
  666. help
  667. Say yes if you want to support the I2C bus on Acorn platforms.
  668. If you don't know, say Y.
  669. config I2C_ELEKTOR
  670. tristate "Elektor ISA card"
  671. depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
  672. select I2C_ALGOPCF
  673. help
  674. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  675. such an adapter.
  676. This support is also available as a module. If so, the module
  677. will be called i2c-elektor.
  678. config I2C_PCA_ISA
  679. tristate "PCA9564/PCA9665 on an ISA bus"
  680. depends on ISA
  681. select I2C_ALGOPCA
  682. default n
  683. help
  684. This driver supports ISA boards using the Philips PCA9564/PCA9665
  685. parallel bus to I2C bus controller.
  686. This driver can also be built as a module. If so, the module
  687. will be called i2c-pca-isa.
  688. This device is almost undetectable and using this driver on a
  689. system which doesn't have this device will result in long
  690. delays when I2C/SMBus chip drivers are loaded (e.g. at boot
  691. time). If unsure, say N.
  692. config I2C_SIBYTE
  693. tristate "SiByte SMBus interface"
  694. depends on SIBYTE_SB1xxx_SOC
  695. help
  696. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  697. config I2C_STUB
  698. tristate "I2C/SMBus Test Stub"
  699. depends on EXPERIMENTAL && m
  700. default 'n'
  701. help
  702. This module may be useful to developers of SMBus client drivers,
  703. especially for certain kinds of sensor chips.
  704. If you do build this module, be sure to read the notes and warnings
  705. in <file:Documentation/i2c/i2c-stub>.
  706. If you don't know what to do here, definitely say N.
  707. config SCx200_I2C
  708. tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
  709. depends on SCx200_GPIO
  710. select I2C_ALGOBIT
  711. help
  712. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  713. If you don't know what to do here, say N.
  714. This support is also available as a module. If so, the module
  715. will be called scx200_i2c.
  716. This driver is deprecated and will be dropped soon. Use i2c-gpio
  717. (or scx200_acb) instead.
  718. config SCx200_I2C_SCL
  719. int "GPIO pin used for SCL"
  720. depends on SCx200_I2C
  721. default "12"
  722. help
  723. Enter the GPIO pin number used for the SCL signal. This value can
  724. also be specified with a module parameter.
  725. config SCx200_I2C_SDA
  726. int "GPIO pin used for SDA"
  727. depends on SCx200_I2C
  728. default "13"
  729. help
  730. Enter the GPIO pin number used for the SSA signal. This value can
  731. also be specified with a module parameter.
  732. config SCx200_ACB
  733. tristate "Geode ACCESS.bus support"
  734. depends on X86_32 && PCI
  735. help
  736. Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
  737. SC1100 processors and the CS5535 and CS5536 Geode companion devices.
  738. If you don't know what to do here, say N.
  739. This support is also available as a module. If so, the module
  740. will be called scx200_acb.
  741. endmenu