Kconfig 27 KB

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