Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675
  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 && BROKEN
  65. help
  66. This supports the use of the I2C interface on Atmel AT91
  67. processors.
  68. This driver is BROKEN because the controller which it uses
  69. will easily trigger RX overrun and TX underrun errors. Using
  70. low I2C clock rates may partially work around those issues
  71. on some systems. Another serious problem is that there is no
  72. documented way to issue repeated START conditions, as needed
  73. to support combined I2C messages. Use the i2c-gpio driver
  74. unless your system can cope with those limitations.
  75. config I2C_AU1550
  76. tristate "Au1550/Au1200 SMBus interface"
  77. depends on SOC_AU1550 || SOC_AU1200
  78. help
  79. If you say yes to this option, support will be included for the
  80. Au1550 and Au1200 SMBus interface.
  81. This driver can also be built as a module. If so, the module
  82. will be called i2c-au1550.
  83. config I2C_BLACKFIN_TWI
  84. tristate "Blackfin TWI I2C support"
  85. depends on BF534 || BF536 || BF537
  86. help
  87. This is the TWI I2C device driver for Blackfin 534/536/537/54x.
  88. This driver can also be built as a module. If so, the module
  89. will be called i2c-bfin-twi.
  90. config I2C_BLACKFIN_TWI_CLK_KHZ
  91. int "Blackfin TWI I2C clock (kHz)"
  92. depends on I2C_BLACKFIN_TWI
  93. range 10 400
  94. default 50
  95. help
  96. The unit of the TWI clock is kHz.
  97. config I2C_DAVINCI
  98. tristate "DaVinci I2C driver"
  99. depends on ARCH_DAVINCI
  100. help
  101. Support for TI DaVinci I2C controller driver.
  102. This driver can also be built as a module. If so, the module
  103. will be called i2c-davinci.
  104. Please note that this driver might be needed to bring up other
  105. devices such as DaVinci NIC.
  106. For details please see http://www.ti.com/davinci
  107. config I2C_ELEKTOR
  108. tristate "Elektor ISA card"
  109. depends on ISA && BROKEN_ON_SMP
  110. select I2C_ALGOPCF
  111. help
  112. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  113. such an adapter.
  114. This support is also available as a module. If so, the module
  115. will be called i2c-elektor.
  116. config I2C_GPIO
  117. tristate "GPIO-based bitbanging I2C"
  118. depends on GENERIC_GPIO
  119. select I2C_ALGOBIT
  120. help
  121. This is a very simple bitbanging I2C driver utilizing the
  122. arch-neutral GPIO API to control the SCL and SDA lines.
  123. config I2C_HYDRA
  124. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  125. depends on PCI && PPC_CHRP && EXPERIMENTAL
  126. select I2C_ALGOBIT
  127. help
  128. This supports the use of the I2C interface in the Apple Hydra Mac
  129. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  130. have such a machine.
  131. This support is also available as a module. If so, the module
  132. will be called i2c-hydra.
  133. config I2C_I801
  134. tristate "Intel 82801 (ICH)"
  135. depends on PCI
  136. help
  137. If you say yes to this option, support will be included for the Intel
  138. 801 family of mainboard I2C interfaces. Specifically, the following
  139. versions of the chipset are supported:
  140. 82801AA
  141. 82801AB
  142. 82801BA
  143. 82801CA/CAM
  144. 82801DB
  145. 82801EB/ER (ICH5/ICH5R)
  146. 6300ESB
  147. ICH6
  148. ICH7
  149. ESB2
  150. ICH8
  151. ICH9
  152. Tolapai
  153. ICH10
  154. This driver can also be built as a module. If so, the module
  155. will be called i2c-i801.
  156. config I2C_I810
  157. tristate "Intel 810/815 (DEPRECATED)"
  158. default n
  159. depends on PCI
  160. select I2C_ALGOBIT
  161. help
  162. If you say yes to this option, support will be included for the Intel
  163. 810/815 family of mainboard I2C interfaces. Specifically, the
  164. following versions of the chipset are supported:
  165. i810AA
  166. i810AB
  167. i810E
  168. i815
  169. i845G
  170. This driver is deprecated in favor of the i810fb and intelfb drivers.
  171. This driver can also be built as a module. If so, the module
  172. will be called i2c-i810.
  173. config I2C_PXA
  174. tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
  175. depends on EXPERIMENTAL && ARCH_PXA
  176. help
  177. If you have devices in the PXA I2C bus, say yes to this option.
  178. This driver can also be built as a module. If so, the module
  179. will be called i2c-pxa.
  180. config I2C_PXA_SLAVE
  181. bool "Intel PXA2XX I2C Slave comms support"
  182. depends on I2C_PXA
  183. help
  184. Support I2C slave mode communications on the PXA I2C bus. This
  185. is necessary for systems where the PXA may be a target on the
  186. I2C bus.
  187. config I2C_PIIX4
  188. tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
  189. depends on PCI
  190. help
  191. If you say yes to this option, support will be included for the Intel
  192. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  193. versions of the chipset are supported (note that Serverworks is part
  194. of Broadcom):
  195. Intel PIIX4
  196. Intel 440MX
  197. ATI IXP200
  198. ATI IXP300
  199. ATI IXP400
  200. ATI SB600
  201. ATI SB700
  202. ATI SB800
  203. Serverworks OSB4
  204. Serverworks CSB5
  205. Serverworks CSB6
  206. Serverworks HT-1000
  207. SMSC Victory66
  208. This driver can also be built as a module. If so, the module
  209. will be called i2c-piix4.
  210. config I2C_IBM_IIC
  211. tristate "IBM PPC 4xx on-chip I2C interface"
  212. depends on IBM_OCP
  213. help
  214. Say Y here if you want to use IIC peripheral found on
  215. embedded IBM PPC 4xx based systems.
  216. This driver can also be built as a module. If so, the module
  217. will be called i2c-ibm_iic.
  218. config I2C_IOP3XX
  219. tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
  220. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
  221. help
  222. Say Y here if you want to use the IIC bus controller on
  223. the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
  224. This driver can also be built as a module. If so, the module
  225. will be called i2c-iop3xx.
  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 PowerMac
  244. platform, and 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 (DEPRECATED)"
  328. default n
  329. depends on PCI
  330. select I2C_ALGOBIT
  331. help
  332. If you say yes to this option, support will be included for the
  333. I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
  334. graphics processors.
  335. chipsets supported:
  336. S3/VIA KM266/VT8375 aka ProSavage8
  337. S3/VIA KM133/VT8365 aka Savage4
  338. This driver is deprecated in favor of the savagefb driver.
  339. This support is also available as a module. If so, the module
  340. will be called i2c-prosavage.
  341. config I2C_S3C2410
  342. tristate "S3C2410 I2C Driver"
  343. depends on ARCH_S3C2410
  344. help
  345. Say Y here to include support for I2C controller in the
  346. Samsung S3C2410 based System-on-Chip devices.
  347. config I2C_SAVAGE4
  348. tristate "S3 Savage 4 (DEPRECATED)"
  349. default n
  350. depends on PCI
  351. select I2C_ALGOBIT
  352. help
  353. If you say yes to this option, support will be included for the
  354. S3 Savage 4 I2C interface.
  355. This driver is deprecated in favor of the savagefb driver.
  356. This driver can also be built as a module. If so, the module
  357. will be called i2c-savage4.
  358. config I2C_SIBYTE
  359. tristate "SiByte SMBus interface"
  360. depends on SIBYTE_SB1xxx_SOC
  361. help
  362. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  363. config I2C_SIMTEC
  364. tristate "Simtec Generic I2C interface"
  365. select I2C_ALGOBIT
  366. help
  367. If you say yes to this option, support will be included for
  368. the Simtec Generic I2C interface. This driver is for the
  369. simple I2C bus used on newer Simtec products for general
  370. I2C, such as DDC on the Simtec BBD2016A.
  371. This driver can also be built as a module. If so, the module
  372. will be called i2c-simtec.
  373. config SCx200_I2C
  374. tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
  375. depends on SCx200_GPIO
  376. select I2C_ALGOBIT
  377. help
  378. Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
  379. If you don't know what to do here, say N.
  380. This support is also available as a module. If so, the module
  381. will be called scx200_i2c.
  382. This driver is deprecated and will be dropped soon. Use i2c-gpio
  383. (or scx200_acb) instead.
  384. config SCx200_I2C_SCL
  385. int "GPIO pin used for SCL"
  386. depends on SCx200_I2C
  387. default "12"
  388. help
  389. Enter the GPIO pin number used for the SCL signal. This value can
  390. also be specified with a module parameter.
  391. config SCx200_I2C_SDA
  392. int "GPIO pin used for SDA"
  393. depends on SCx200_I2C
  394. default "13"
  395. help
  396. Enter the GPIO pin number used for the SSA signal. This value can
  397. also be specified with a module parameter.
  398. config SCx200_ACB
  399. tristate "Geode ACCESS.bus support"
  400. depends on X86_32 && PCI
  401. help
  402. Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
  403. SC1100 processors and the CS5535 and CS5536 Geode companion devices.
  404. If you don't know what to do here, say N.
  405. This support is also available as a module. If so, the module
  406. will be called scx200_acb.
  407. config I2C_SIS5595
  408. tristate "SiS 5595"
  409. depends on PCI
  410. help
  411. If you say yes to this option, support will be included for the
  412. SiS5595 SMBus (a subset of I2C) interface.
  413. This driver can also be built as a module. If so, the module
  414. will be called i2c-sis5595.
  415. config I2C_SIS630
  416. tristate "SiS 630/730"
  417. depends on PCI
  418. help
  419. If you say yes to this option, support will be included for the
  420. SiS630 and SiS730 SMBus (a subset of I2C) interface.
  421. This driver can also be built as a module. If so, the module
  422. will be called i2c-sis630.
  423. config I2C_SIS96X
  424. tristate "SiS 96x"
  425. depends on PCI
  426. help
  427. If you say yes to this option, support will be included for the SiS
  428. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  429. chipsets are supported:
  430. 645/961
  431. 645DX/961
  432. 645DX/962
  433. 648/961
  434. 650/961
  435. 735
  436. 745
  437. This driver can also be built as a module. If so, the module
  438. will be called i2c-sis96x.
  439. config I2C_TAOS_EVM
  440. tristate "TAOS evaluation module"
  441. depends on EXPERIMENTAL
  442. select SERIO
  443. select SERIO_SERPORT
  444. default n
  445. help
  446. This supports TAOS evaluation modules on serial port. In order to
  447. use this driver, you will need the inputattach tool, which is part
  448. of the input-utils package.
  449. If unsure, say N.
  450. This support is also available as a module. If so, the module
  451. will be called i2c-taos-evm.
  452. config I2C_STUB
  453. tristate "I2C/SMBus Test Stub"
  454. depends on EXPERIMENTAL && m
  455. default 'n'
  456. help
  457. This module may be useful to developers of SMBus client drivers,
  458. especially for certain kinds of sensor chips.
  459. If you do build this module, be sure to read the notes and warnings
  460. in <file:Documentation/i2c/i2c-stub>.
  461. If you don't know what to do here, definitely say N.
  462. config I2C_TINY_USB
  463. tristate "I2C-Tiny-USB"
  464. depends on USB
  465. help
  466. If you say yes to this option, support will be included for the
  467. i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
  468. http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
  469. This driver can also be built as a module. If so, the module
  470. will be called i2c-tiny-usb.
  471. config I2C_VERSATILE
  472. tristate "ARM Versatile/Realview I2C bus support"
  473. depends on ARCH_VERSATILE || ARCH_REALVIEW
  474. select I2C_ALGOBIT
  475. help
  476. Say yes if you want to support the I2C serial bus on ARMs Versatile
  477. range of platforms.
  478. This driver can also be built as a module. If so, the module
  479. will be called i2c-versatile.
  480. config I2C_ACORN
  481. tristate "Acorn IOC/IOMD I2C bus support"
  482. depends on ARCH_ACORN
  483. default y
  484. select I2C_ALGOBIT
  485. help
  486. Say yes if you want to support the I2C bus on Acorn platforms.
  487. If you don't know, say Y.
  488. config I2C_VIA
  489. tristate "VIA 82C586B"
  490. depends on PCI && EXPERIMENTAL
  491. select I2C_ALGOBIT
  492. help
  493. If you say yes to this option, support will be included for the VIA
  494. 82C586B I2C interface
  495. This driver can also be built as a module. If so, the module
  496. will be called i2c-via.
  497. config I2C_VIAPRO
  498. tristate "VIA VT82C596/82C686/82xx and CX700"
  499. depends on PCI
  500. help
  501. If you say yes to this option, support will be included for the VIA
  502. VT82C596 and later SMBus interface. Specifically, the following
  503. chipsets are supported:
  504. VT82C596A/B
  505. VT82C686A/B
  506. VT8231
  507. VT8233/A
  508. VT8235
  509. VT8237R/A/S
  510. VT8251
  511. CX700
  512. This driver can also be built as a module. If so, the module
  513. will be called i2c-viapro.
  514. config I2C_VOODOO3
  515. tristate "Voodoo 3"
  516. depends on PCI
  517. select I2C_ALGOBIT
  518. help
  519. If you say yes to this option, support will be included for the
  520. Voodoo 3 I2C interface.
  521. This driver can also be built as a module. If so, the module
  522. will be called i2c-voodoo3.
  523. config I2C_PCA_ISA
  524. tristate "PCA9564 on an ISA bus"
  525. depends on ISA
  526. select I2C_ALGOPCA
  527. default n
  528. help
  529. This driver supports ISA boards using the Philips PCA 9564
  530. Parallel bus to I2C bus controller
  531. This driver can also be built as a module. If so, the module
  532. will be called i2c-pca-isa.
  533. This device is almost undetectable and using this driver on a
  534. system which doesn't have this device will result in long
  535. delays when I2C/SMBus chip drivers are loaded (e.g. at boot
  536. time). If unsure, say N.
  537. config I2C_MV64XXX
  538. tristate "Marvell mv64xxx I2C Controller"
  539. depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
  540. help
  541. If you say yes to this option, support will be included for the
  542. built-in I2C interface on the Marvell 64xxx line of host bridges.
  543. This driver can also be built as a module. If so, the module
  544. will be called i2c-mv64xxx.
  545. config I2C_PNX
  546. tristate "I2C bus support for Philips PNX targets"
  547. depends on ARCH_PNX4008
  548. help
  549. This driver supports the Philips IP3204 I2C IP block master and/or
  550. slave controller
  551. This driver can also be built as a module. If so, the module
  552. will be called i2c-pnx.
  553. config I2C_PMCMSP
  554. tristate "PMC MSP I2C TWI Controller"
  555. depends on PMC_MSP
  556. help
  557. This driver supports the PMC TWI controller on MSP devices.
  558. This driver can also be built as module. If so, the module
  559. will be called i2c-pmcmsp.
  560. endmenu