Kconfig 20 KB

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