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