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