Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715
  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 && 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)"
  66. depends on PCI
  67. help
  68. If you say yes to this option, support will be included for the Intel
  69. 801 family of mainboard I2C interfaces. Specifically, the following
  70. versions of the chipset are supported:
  71. 82801AA
  72. 82801AB
  73. 82801BA
  74. 82801CA/CAM
  75. 82801DB
  76. 82801EB/ER (ICH5/ICH5R)
  77. 6300ESB
  78. ICH6
  79. ICH7
  80. ESB2
  81. ICH8
  82. ICH9
  83. Tolapai
  84. ICH10
  85. This driver can also be built as a module. If so, the module
  86. will be called i2c-i801.
  87. config I2C_ISCH
  88. tristate "Intel SCH SMBus 1.0"
  89. depends on PCI
  90. help
  91. Say Y here if you want to use SMBus controller on the Intel SCH
  92. based systems.
  93. This driver can also be built as a module. If so, the module
  94. will be called i2c-isch.
  95. config I2C_PIIX4
  96. tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
  97. depends on PCI
  98. help
  99. If you say yes to this option, support will be included for the Intel
  100. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  101. versions of the chipset are supported (note that Serverworks is part
  102. of Broadcom):
  103. Intel PIIX4
  104. Intel 440MX
  105. ATI IXP200
  106. ATI IXP300
  107. ATI IXP400
  108. ATI SB600
  109. ATI SB700
  110. ATI SB800
  111. Serverworks OSB4
  112. Serverworks CSB5
  113. Serverworks CSB6
  114. Serverworks HT-1000
  115. SMSC Victory66
  116. This driver can also be built as a module. If so, the module
  117. will be called i2c-piix4.
  118. config I2C_NFORCE2
  119. tristate "Nvidia nForce2, nForce3 and nForce4"
  120. depends on PCI
  121. help
  122. If you say yes to this option, support will be included for the Nvidia
  123. nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
  124. This driver can also be built as a module. If so, the module
  125. will be called i2c-nforce2.
  126. config I2C_NFORCE2_S4985
  127. tristate "SMBus multiplexing on the Tyan S4985"
  128. depends on I2C_NFORCE2 && EXPERIMENTAL
  129. help
  130. Enabling this option will add specific SMBus support for the Tyan
  131. S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
  132. over 4 different channels, where the various memory module EEPROMs
  133. live. Saying yes here will give you access to these in addition
  134. to the trunk.
  135. This driver can also be built as a module. If so, the module
  136. will be called i2c-nforce2-s4985.
  137. config I2C_SIS5595
  138. tristate "SiS 5595"
  139. depends on PCI
  140. help
  141. If you say yes to this option, support will be included for the
  142. SiS5595 SMBus (a subset of I2C) interface.
  143. This driver can also be built as a module. If so, the module
  144. will be called i2c-sis5595.
  145. config I2C_SIS630
  146. tristate "SiS 630/730"
  147. depends on PCI
  148. help
  149. If you say yes to this option, support will be included for the
  150. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  151. This driver can also be built as a module. If so, the module
  152. will be called i2c-sis630.
  153. config I2C_SIS96X
  154. tristate "SiS 96x"
  155. depends on PCI
  156. help
  157. If you say yes to this option, support will be included for the SiS
  158. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  159. chipsets are supported:
  160. 645/961
  161. 645DX/961
  162. 645DX/962
  163. 648/961
  164. 650/961
  165. 735
  166. 745
  167. This driver can also be built as a module. If so, the module
  168. will be called i2c-sis96x.
  169. config I2C_VIA
  170. tristate "VIA VT82C586B"
  171. depends on PCI && EXPERIMENTAL
  172. select I2C_ALGOBIT
  173. help
  174. If you say yes to this option, support will be included for the VIA
  175. 82C586B I2C interface
  176. This driver can also be built as a module. If so, the module
  177. will be called i2c-via.
  178. config I2C_VIAPRO
  179. tristate "VIA VT82C596/82C686/82xx and CX700"
  180. depends on PCI
  181. help
  182. If you say yes to this option, support will be included for the VIA
  183. VT82C596 and later SMBus interface. Specifically, the following
  184. chipsets are supported:
  185. VT82C596A/B
  186. VT82C686A/B
  187. VT8231
  188. VT8233/A
  189. VT8235
  190. VT8237R/A/S
  191. VT8251
  192. CX700
  193. This driver can also be built as a module. If so, the module
  194. will be called i2c-viapro.
  195. comment "Mac SMBus host controller drivers"
  196. depends on PPC_CHRP || PPC_PMAC
  197. config I2C_HYDRA
  198. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  199. depends on PCI && PPC_CHRP && EXPERIMENTAL
  200. select I2C_ALGOBIT
  201. help
  202. This supports the use of the I2C interface in the Apple Hydra Mac
  203. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  204. have such a machine.
  205. This support is also available as a module. If so, the module
  206. will be called i2c-hydra.
  207. config I2C_POWERMAC
  208. tristate "Powermac I2C interface"
  209. depends on PPC_PMAC
  210. default y
  211. help
  212. This exposes the various PowerMac i2c interfaces to the linux i2c
  213. layer and to userland. It is used by various drivers on the PowerMac
  214. platform, and should generally be enabled.
  215. This support is also available as a module. If so, the module
  216. will be called i2c-powermac.
  217. comment "I2C system bus drivers (mostly embedded / system-on-chip)"
  218. config I2C_AT91
  219. tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
  220. depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
  221. help
  222. This supports the use of the I2C interface on Atmel AT91
  223. processors.
  224. This driver is BROKEN because the controller which it uses
  225. will easily trigger RX overrun and TX underrun errors. Using
  226. low I2C clock rates may partially work around those issues
  227. on some systems. Another serious problem is that there is no
  228. documented way to issue repeated START conditions, as needed
  229. to support combined I2C messages. Use the i2c-gpio driver
  230. unless your system can cope with those limitations.
  231. config I2C_AU1550
  232. tristate "Au1550/Au1200 SMBus interface"
  233. depends on SOC_AU1550 || SOC_AU1200
  234. help
  235. If you say yes to this option, support will be included for the
  236. Au1550 and Au1200 SMBus interface.
  237. This driver can also be built as a module. If so, the module
  238. will be called i2c-au1550.
  239. config I2C_BLACKFIN_TWI
  240. tristate "Blackfin TWI I2C support"
  241. depends on BLACKFIN
  242. depends on !BF561 && !BF531 && !BF532 && !BF533
  243. help
  244. This is the I2C bus driver for Blackfin on-chip TWI interface.
  245. This driver can also be built as a module. If so, the module
  246. will be called i2c-bfin-twi.
  247. config I2C_BLACKFIN_TWI_CLK_KHZ
  248. int "Blackfin TWI I2C clock (kHz)"
  249. depends on I2C_BLACKFIN_TWI
  250. range 10 400
  251. default 50
  252. help
  253. The unit of the TWI clock is kHz.
  254. config I2C_CPM
  255. tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
  256. depends on (CPM1 || CPM2) && OF_I2C
  257. help
  258. This supports the use of the I2C interface on Freescale
  259. processors with CPM1 or CPM2.
  260. This driver can also be built as a module. If so, the module
  261. will be called i2c-cpm.
  262. config I2C_DAVINCI
  263. tristate "DaVinci I2C driver"
  264. depends on ARCH_DAVINCI
  265. help
  266. Support for TI DaVinci I2C controller driver.
  267. This driver can also be built as a module. If so, the module
  268. will be called i2c-davinci.
  269. Please note that this driver might be needed to bring up other
  270. devices such as DaVinci NIC.
  271. For details please see http://www.ti.com/davinci
  272. config I2C_GPIO
  273. tristate "GPIO-based bitbanging I2C"
  274. depends on GENERIC_GPIO
  275. select I2C_ALGOBIT
  276. help
  277. This is a very simple bitbanging I2C driver utilizing the
  278. arch-neutral GPIO API to control the SCL and SDA lines.
  279. config I2C_HIGHLANDER
  280. tristate "Highlander FPGA SMBus interface"
  281. depends on SH_HIGHLANDER
  282. help
  283. If you say yes to this option, support will be included for
  284. the SMBus interface located in the FPGA on various Highlander
  285. boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
  286. FPGAs. This is wholly unrelated to the SoC I2C.
  287. This driver can also be built as a module. If so, the module
  288. will be called i2c-highlander.
  289. config I2C_IBM_IIC
  290. tristate "IBM PPC 4xx on-chip I2C interface"
  291. depends on 4xx
  292. help
  293. Say Y here if you want to use IIC peripheral found on
  294. embedded IBM PPC 4xx based systems.
  295. This driver can also be built as a module. If so, the module
  296. will be called i2c-ibm_iic.
  297. config I2C_IOP3XX
  298. tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
  299. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
  300. help
  301. Say Y here if you want to use the IIC bus controller on
  302. the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
  303. This driver can also be built as a module. If so, the module
  304. will be called i2c-iop3xx.
  305. config I2C_IXP2000
  306. tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
  307. depends on ARCH_IXP2000
  308. select I2C_ALGOBIT
  309. help
  310. Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
  311. system and are using GPIO lines for an I2C bus.
  312. This support is also available as a module. If so, the module
  313. will be called i2c-ixp2000.
  314. This driver is deprecated and will be dropped soon. Use i2c-gpio
  315. instead.
  316. config I2C_MPC
  317. tristate "MPC107/824x/85xx/52xx/86xx"
  318. depends on PPC32
  319. help
  320. If you say yes to this option, support will be included for the
  321. built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
  322. MPC85xx/MPC8641 family processors. The driver may also work on 52xx
  323. family processors, though interrupts are known not to work.
  324. This driver can also be built as a module. If so, the module
  325. will be called i2c-mpc.
  326. config I2C_MV64XXX
  327. tristate "Marvell mv64xxx I2C Controller"
  328. depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
  329. help
  330. If you say yes to this option, support will be included for the
  331. built-in I2C interface on the Marvell 64xxx line of host bridges.
  332. This driver can also be built as a module. If so, the module
  333. will be called i2c-mv64xxx.
  334. config I2C_OCORES
  335. tristate "OpenCores I2C Controller"
  336. depends on EXPERIMENTAL
  337. help
  338. If you say yes to this option, support will be included for the
  339. OpenCores I2C controller. For details see
  340. http://www.opencores.org/projects.cgi/web/i2c/overview
  341. This driver can also be built as a module. If so, the module
  342. will be called i2c-ocores.
  343. config I2C_OMAP
  344. tristate "OMAP I2C adapter"
  345. depends on ARCH_OMAP
  346. default y if MACH_OMAP_H3 || MACH_OMAP_OSK
  347. help
  348. If you say yes to this option, support will be included for the
  349. I2C interface on the Texas Instruments OMAP1/2 family of processors.
  350. Like OMAP1510/1610/1710/5912 and OMAP242x.
  351. For details see http://www.ti.com/omap.
  352. config I2C_PASEMI
  353. tristate "PA Semi SMBus interface"
  354. depends on PPC_PASEMI && PCI
  355. help
  356. Supports the PA Semi PWRficient on-chip SMBus interfaces.
  357. config I2C_PNX
  358. tristate "I2C bus support for Philips PNX targets"
  359. depends on ARCH_PNX4008
  360. help
  361. This driver supports the Philips IP3204 I2C IP block master and/or
  362. slave controller
  363. This driver can also be built as a module. If so, the module
  364. will be called i2c-pnx.
  365. config I2C_PXA
  366. tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
  367. depends on EXPERIMENTAL && ARCH_PXA
  368. help
  369. If you have devices in the PXA I2C bus, say yes to this option.
  370. This driver can also be built as a module. If so, the module
  371. will be called i2c-pxa.
  372. config I2C_PXA_SLAVE
  373. bool "Intel PXA2XX I2C Slave comms support"
  374. depends on I2C_PXA
  375. help
  376. Support I2C slave mode communications on the PXA I2C bus. This
  377. is necessary for systems where the PXA may be a target on the
  378. I2C bus.
  379. config I2C_S3C2410
  380. tristate "S3C2410 I2C Driver"
  381. depends on ARCH_S3C2410
  382. help
  383. Say Y here to include support for I2C controller in the
  384. Samsung S3C2410 based System-on-Chip devices.
  385. config I2C_SH7760
  386. tristate "Renesas SH7760 I2C Controller"
  387. depends on CPU_SUBTYPE_SH7760
  388. help
  389. This driver supports the 2 I2C interfaces on the Renesas SH7760.
  390. This driver can also be built as a module. If so, the module
  391. will be called i2c-sh7760.
  392. config I2C_SH_MOBILE
  393. tristate "SuperH Mobile I2C Controller"
  394. depends on SUPERH
  395. help
  396. If you say yes to this option, support will be included for the
  397. built-in I2C interface on the Renesas SH-Mobile processor.
  398. This driver can also be built as a module. If so, the module
  399. will be called i2c-sh_mobile.
  400. config I2C_SIMTEC
  401. tristate "Simtec Generic I2C interface"
  402. select I2C_ALGOBIT
  403. help
  404. If you say yes to this option, support will be included for
  405. the Simtec Generic I2C interface. This driver is for the
  406. simple I2C bus used on newer Simtec products for general
  407. I2C, such as DDC on the Simtec BBD2016A.
  408. This driver can also be built as a module. If so, the module
  409. will be called i2c-simtec.
  410. config I2C_VERSATILE
  411. tristate "ARM Versatile/Realview I2C bus support"
  412. depends on ARCH_VERSATILE || ARCH_REALVIEW
  413. select I2C_ALGOBIT
  414. help
  415. Say yes if you want to support the I2C serial bus on ARMs Versatile
  416. range of platforms.
  417. This driver can also be built as a module. If so, the module
  418. will be called i2c-versatile.
  419. comment "External I2C/SMBus adapter drivers"
  420. config I2C_PARPORT
  421. tristate "Parallel port adapter"
  422. depends on PARPORT
  423. select I2C_ALGOBIT
  424. help
  425. This supports parallel port I2C adapters such as the ones made by
  426. Philips or Velleman, Analog Devices evaluation boards, and more.
  427. Basically any adapter using the parallel port as an I2C bus with
  428. no extra chipset is supported by this driver, or could be.
  429. This driver is a replacement for (and was inspired by) an older
  430. driver named i2c-philips-par. The new driver supports more devices,
  431. and makes it easier to add support for new devices.
  432. An adapter type parameter is now mandatory. Please read the file
  433. Documentation/i2c/busses/i2c-parport for details.
  434. Another driver exists, named i2c-parport-light, which doesn't depend
  435. on the parport driver. This is meant for embedded systems. Don't say
  436. Y here if you intend to say Y or M there.
  437. This support is also available as a module. If so, the module
  438. will be called i2c-parport.
  439. config I2C_PARPORT_LIGHT
  440. tristate "Parallel port adapter (light)"
  441. select I2C_ALGOBIT
  442. help
  443. This supports parallel port I2C adapters such as the ones made by
  444. Philips or Velleman, Analog Devices evaluation boards, and more.
  445. Basically any adapter using the parallel port as an I2C bus with
  446. no extra chipset is supported by this driver, or could be.
  447. This driver is a light version of i2c-parport. It doesn't depend
  448. on the parport driver, and uses direct I/O access instead. This
  449. might be preferred on embedded systems where wasting memory for
  450. the clean but heavy parport handling is not an option. The
  451. drawback is a reduced portability and the impossibility to
  452. daisy-chain other parallel port devices.
  453. Don't say Y here if you said Y or M to i2c-parport. Saying M to
  454. both is possible but both modules should not be loaded at the same
  455. time.
  456. This support is also available as a module. If so, the module
  457. will be called i2c-parport-light.
  458. config I2C_TAOS_EVM
  459. tristate "TAOS evaluation module"
  460. depends on EXPERIMENTAL
  461. select SERIO
  462. select SERIO_SERPORT
  463. default n
  464. help
  465. This supports TAOS evaluation modules on serial port. In order to
  466. use this driver, you will need the inputattach tool, which is part
  467. of the input-utils package.
  468. If unsure, say N.
  469. This support is also available as a module. If so, the module
  470. will be called i2c-taos-evm.
  471. config I2C_TINY_USB
  472. tristate "Tiny-USB adapter"
  473. depends on USB
  474. help
  475. If you say yes to this option, support will be included for the
  476. i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
  477. http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
  478. This driver can also be built as a module. If so, the module
  479. will be called i2c-tiny-usb.
  480. comment "Graphics adapter I2C/DDC channel drivers"
  481. depends on PCI
  482. config I2C_VOODOO3
  483. tristate "Voodoo 3"
  484. depends on PCI
  485. select I2C_ALGOBIT
  486. help
  487. If you say yes to this option, support will be included for the
  488. Voodoo 3 I2C interface.
  489. This driver can also be built as a module. If so, the module
  490. will be called i2c-voodoo3.
  491. comment "Other I2C/SMBus bus drivers"
  492. config I2C_ACORN
  493. tristate "Acorn IOC/IOMD I2C bus support"
  494. depends on ARCH_ACORN
  495. default y
  496. select I2C_ALGOBIT
  497. help
  498. Say yes if you want to support the I2C bus on Acorn platforms.
  499. If you don't know, say Y.
  500. config I2C_ELEKTOR
  501. tristate "Elektor ISA card"
  502. depends on ISA && BROKEN_ON_SMP
  503. select I2C_ALGOPCF
  504. help
  505. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  506. such an adapter.
  507. This support is also available as a module. If so, the module
  508. will be called i2c-elektor.
  509. config I2C_PCA_ISA
  510. tristate "PCA9564 on an ISA bus"
  511. depends on ISA
  512. select I2C_ALGOPCA
  513. default n
  514. help
  515. This driver supports ISA boards using the Philips PCA9564
  516. parallel bus to I2C bus controller.
  517. This driver can also be built as a module. If so, the module
  518. will be called i2c-pca-isa.
  519. This device is almost undetectable and using this driver on a
  520. system which doesn't have this device will result in long
  521. delays when I2C/SMBus chip drivers are loaded (e.g. at boot
  522. time). If unsure, say N.
  523. config I2C_PCA_PLATFORM
  524. tristate "PCA9564 as platform device"
  525. select I2C_ALGOPCA
  526. default n
  527. help
  528. This driver supports a memory mapped Philips PCA9564
  529. parallel bus to I2C bus controller.
  530. This driver can also be built as a module. If so, the module
  531. will be called i2c-pca-platform.
  532. config I2C_PMCMSP
  533. tristate "PMC MSP I2C TWI Controller"
  534. depends on PMC_MSP
  535. help
  536. This driver supports the PMC TWI controller on MSP devices.
  537. This driver can also be built as module. If so, the module
  538. will be called i2c-pmcmsp.
  539. config I2C_SIBYTE
  540. tristate "SiByte SMBus interface"
  541. depends on SIBYTE_SB1xxx_SOC
  542. help
  543. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  544. config I2C_STUB
  545. tristate "I2C/SMBus Test Stub"
  546. depends on EXPERIMENTAL && m
  547. default 'n'
  548. help
  549. This module may be useful to developers of SMBus client drivers,
  550. especially for certain kinds of sensor chips.
  551. If you do build this module, be sure to read the notes and warnings
  552. in <file:Documentation/i2c/i2c-stub>.
  553. If you don't know what to do here, definitely say N.
  554. config SCx200_I2C
  555. tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
  556. depends on SCx200_GPIO
  557. select I2C_ALGOBIT
  558. help
  559. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  560. If you don't know what to do here, say N.
  561. This support is also available as a module. If so, the module
  562. will be called scx200_i2c.
  563. This driver is deprecated and will be dropped soon. Use i2c-gpio
  564. (or scx200_acb) instead.
  565. config SCx200_I2C_SCL
  566. int "GPIO pin used for SCL"
  567. depends on SCx200_I2C
  568. default "12"
  569. help
  570. Enter the GPIO pin number used for the SCL signal. This value can
  571. also be specified with a module parameter.
  572. config SCx200_I2C_SDA
  573. int "GPIO pin used for SDA"
  574. depends on SCx200_I2C
  575. default "13"
  576. help
  577. Enter the GPIO pin number used for the SSA signal. This value can
  578. also be specified with a module parameter.
  579. config SCx200_ACB
  580. tristate "Geode ACCESS.bus support"
  581. depends on X86_32 && PCI
  582. help
  583. Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
  584. SC1100 processors and the CS5535 and CS5536 Geode companion devices.
  585. If you don't know what to do here, say N.
  586. This support is also available as a module. If so, the module
  587. will be called scx200_acb.
  588. endmenu