Kconfig 28 KB

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