Kconfig 27 KB

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