[deliverable/linux.git] / drivers / i2c / busses / Kconfig

#
# Sensor device configuration
#

menu "I2C Hardware Bus support"
	depends on I2C

config I2C_ALI1535
	tristate "ALI 1535"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the SMB
	  Host controller on Acer Labs Inc. (ALI) M1535 South Bridges.  The SMB
	  controller is part of the 7101 device, which is an ACPI-compliant
	  Power Management Unit (PMU).

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-ali1535.

config I2C_ALI1563
	tristate "ALI 1563"
	depends on I2C && PCI && EXPERIMENTAL
	help
	  If you say yes to this option, support will be included for the SMB
	  Host controller on Acer Labs Inc. (ALI) M1563 South Bridges.  The SMB
	  controller is part of the 7101 device, which is an ACPI-compliant
	  Power Management Unit (PMU).

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-ali1563.

config I2C_ALI15X3
	tristate "ALI 15x3"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the
	  Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-ali15x3.

config I2C_AMD756
	tristate "AMD 756/766/768/8111 and nVidia nForce"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the AMD
	  756/766/768 mainboard I2C interfaces.  The driver also includes
	  support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
	  the nVidia nForce I2C interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-amd756.

config I2C_AMD756_S4882
	tristate "SMBus multiplexing on the Tyan S4882"
	depends on I2C_AMD756 && EXPERIMENTAL
	help
	  Enabling this option will add specific SMBus support for the Tyan
	  S4882 motherboard.  On this 4-CPU board, the SMBus is multiplexed
	  over 8 different channels, where the various memory module EEPROMs
	  and temperature sensors live.  Saying yes here will give you access
	  to these in addition to the trunk.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-amd756-s4882.

config I2C_AMD8111
	tristate "AMD 8111"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the
	  second (SMBus 2.0) AMD 8111 mainboard I2C interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-amd8111.

config I2C_AU1550
	tristate "Au1550 SMBus interface"
	depends on I2C && SOC_AU1550
	help
	  If you say yes to this option, support will be included for the
	  Au1550 SMBus interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-au1550.

config I2C_ELEKTOR
	tristate "Elektor ISA card"
	depends on I2C && ISA && BROKEN_ON_SMP
	select I2C_ALGOPCF
	help
	  This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
	  such an adapter.

	  This support is also available as a module.  If so, the module 
	  will be called i2c-elektor.

config I2C_HYDRA
	tristate "CHRP Apple Hydra Mac I/O I2C interface"
	depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
	select I2C_ALGOBIT
	help
	  This supports the use of the I2C interface in the Apple Hydra Mac
	  I/O chip on some CHRP machines (e.g. the LongTrail).  Say Y if you
	  have such a machine.

	  This support is also available as a module.  If so, the module
	  will be called i2c-hydra.

config I2C_I801
	tristate "Intel 82801 (ICH)"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the Intel
	  801 family of mainboard I2C interfaces.  Specifically, the following
	  versions of the chipset are supported:
	    82801AA
	    82801AB
	    82801BA
	    82801CA/CAM
	    82801DB
	    82801EB/ER (ICH5/ICH5R)
	    6300ESB
	    ICH6
	    ICH7
	    ESB2
	    ICH8

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-i801.

config I2C_I810
	tristate "Intel 810/815"
	depends on I2C && PCI
	select I2C_ALGOBIT
	help
	  If you say yes to this option, support will be included for the Intel
	  810/815 family of mainboard I2C interfaces.  Specifically, the 
	  following versions of the chipset are supported:
	    i810AA
	    i810AB
	    i810E
	    i815
	    i845G

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-i810.

config I2C_PXA
	tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
	depends on I2C && EXPERIMENTAL && ARCH_PXA
	help
	  If you have devices in the PXA I2C bus, say yes to this option.
	  This driver can also be built as a module.  If so, the module
	  will be called i2c-pxa.

config I2C_PXA_SLAVE
	bool "Intel PXA2XX I2C Slave comms support"
	depends on I2C_PXA
	help
	  Support I2C slave mode communications on the PXA I2C bus.  This
	  is necessary for systems where the PXA may be a target on the
	  I2C bus.

config I2C_PIIX4
	tristate "Intel PIIX4"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the Intel
	  PIIX4 family of mainboard I2C interfaces.  Specifically, the following
	  versions of the chipset are supported (note that Serverworks is part
	  of Broadcom):
	    Intel PIIX4
	    Intel 440MX
	    Serverworks OSB4
	    Serverworks CSB5
	    Serverworks CSB6
	    Serverworks HT-1000
	    SMSC Victory66

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-piix4.

config I2C_IBM_IIC
	tristate "IBM PPC 4xx on-chip I2C interface"
	depends on IBM_OCP && I2C
	help
	  Say Y here if you want to use IIC peripheral found on 
	  embedded IBM PPC 4xx based systems. 

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-ibm_iic.

config I2C_IOP3XX
	tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
	depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
	help
	  Say Y here if you want to use the IIC bus controller on
	  the Intel IOP3xx I/O Processors or IXP4xx Network Processors.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-iop3xx.

config I2C_ISA
	tristate
	depends on I2C

config I2C_ITE
	tristate "ITE I2C Adapter"
	depends on I2C && MIPS_ITE8172
	select I2C_ALGOITE
	help
	  This supports the ITE8172 I2C peripheral found on some MIPS
	  systems. Say Y if you have one of these. You should also say Y for
	  the ITE I2C driver algorithm support above.

	  This support is also available as a module.  If so, the module 
	  will be called i2c-ite.

config I2C_IXP4XX
	tristate "IXP4xx GPIO-Based I2C Interface"
	depends on I2C && ARCH_IXP4XX
	select I2C_ALGOBIT
	help
	  Say Y here if you have an Intel IXP4xx(420,421,422,425) based 
	  system and are using GPIO lines for an I2C bus.

	  This support is also available as a module. If so, the module
	  will be called i2c-ixp4xx.

config I2C_IXP2000
	tristate "IXP2000 GPIO-Based I2C Interface"
	depends on I2C && ARCH_IXP2000
	select I2C_ALGOBIT
	help
	  Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based 
	  system and are using GPIO lines for an I2C bus.

	  This support is also available as a module. If so, the module
	  will be called i2c-ixp2000.

config I2C_POWERMAC
	tristate "Powermac I2C interface"
	depends on I2C && PPC_PMAC
	default y
	help
	  This exposes the various PowerMac i2c interfaces to the linux i2c
	  layer and to userland. It is used by various drivers on the powemac
	  platform, thus should generally be enabled.

	  This support is also available as a module.  If so, the module
	  will be called i2c-powermac.

config I2C_MPC
	tristate "MPC107/824x/85xx/52xx"
	depends on I2C && PPC32
	help
	  If you say yes to this option, support will be included for the
	  built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
	  MPC85xx family processors. The driver may also work on 52xx
	  family processors, though interrupts are known not to work.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-mpc.

config I2C_NFORCE2
	tristate "Nvidia nForce2, nForce3 and nForce4"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the Nvidia
	  nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-nforce2.

config I2C_PARPORT
	tristate "Parallel port adapter"
	depends on I2C && PARPORT
	select I2C_ALGOBIT
	help
	  This supports parallel port I2C adapters such as the ones made by
	  Philips or Velleman, Analog Devices evaluation boards, and more.
	  Basically any adapter using the parallel port as an I2C bus with
	  no extra chipset is supported by this driver, or could be.

	  This driver is a replacement for (and was inspired by) an older
	  driver named i2c-philips-par.  The new driver supports more devices,
	  and makes it easier to add support for new devices.

	  An adapter type parameter is now mandatory.  Please read the file
	  Documentation/i2c/busses/i2c-parport for details.

	  Another driver exists, named i2c-parport-light, which doesn't depend
	  on the parport driver.  This is meant for embedded systems. Don't say
	  Y here if you intend to say Y or M there.

	  This support is also available as a module.  If so, the module 
	  will be called i2c-parport.

config I2C_PARPORT_LIGHT
	tristate "Parallel port adapter (light)"
	depends on I2C
	select I2C_ALGOBIT
	help
	  This supports parallel port I2C adapters such as the ones made by
	  Philips or Velleman, Analog Devices evaluation boards, and more.
	  Basically any adapter using the parallel port as an I2C bus with
	  no extra chipset is supported by this driver, or could be.

	  This driver is a light version of i2c-parport.  It doesn't depend
	  on the parport driver, and uses direct I/O access instead.  This
	  might be prefered on embedded systems where wasting memory for
	  the clean but heavy parport handling is not an option.  The
	  drawback is a reduced portability and the impossibility to
	  dasiy-chain other parallel port devices.
	  
	  Don't say Y here if you said Y or M to i2c-parport.  Saying M to
	  both is possible but both modules should not be loaded at the same
	  time.

	  This support is also available as a module.  If so, the module 
	  will be called i2c-parport-light.

config I2C_PROSAVAGE
	tristate "S3/VIA (Pro)Savage"
	depends on I2C && PCI
	select I2C_ALGOBIT
	help
	  If you say yes to this option, support will be included for the
	  I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
	  graphics processors.
	  chipsets supported:
	    S3/VIA KM266/VT8375 aka ProSavage8
	    S3/VIA KM133/VT8365 aka Savage4

	  This support is also available as a module.  If so, the module 
	  will be called i2c-prosavage.

config I2C_RPXLITE
	tristate "Embedded Planet RPX Lite/Classic support"
	depends on (RPXLITE || RPXCLASSIC) && I2C
	select I2C_ALGO8XX

config I2C_S3C2410
	tristate "S3C2410 I2C Driver"
	depends on I2C && ARCH_S3C2410
	help
	  Say Y here to include support for I2C controller in the
	  Samsung S3C2410 based System-on-Chip devices.

config I2C_SAVAGE4
	tristate "S3 Savage 4"
	depends on I2C && PCI && EXPERIMENTAL
	select I2C_ALGOBIT
	help
	  If you say yes to this option, support will be included for the 
	  S3 Savage 4 I2C interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-savage4.

config I2C_SIBYTE
	tristate "SiByte SMBus interface"
	depends on SIBYTE_SB1xxx_SOC && I2C
	help
	  Supports the SiByte SOC on-chip I2C interfaces (2 channels).

config SCx200_I2C
	tristate "NatSemi SCx200 I2C using GPIO pins"
	depends on SCx200_GPIO && I2C
	select I2C_ALGOBIT
	help
	  Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.

	  If you don't know what to do here, say N.

	  This support is also available as a module.  If so, the module 
	  will be called scx200_i2c.

config SCx200_I2C_SCL
	int "GPIO pin used for SCL"
	depends on SCx200_I2C
	default "12"
	help
	  Enter the GPIO pin number used for the SCL signal.  This value can
	  also be specified with a module parameter.

config SCx200_I2C_SDA
	int "GPIO pin used for SDA"
	depends on SCx200_I2C
	default "13"
	help
	  Enter the GPIO pin number used for the SSA signal.  This value can
	  also be specified with a module parameter.

config SCx200_ACB
	tristate "Geode ACCESS.bus support"
	depends on X86_32 && I2C && PCI
	help
	  Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
	  SC1100 processors and the CS5535 and CS5536 Geode companion devices.

	  If you don't know what to do here, say N.

	  This support is also available as a module.  If so, the module 
	  will be called scx200_acb.

config I2C_SIS5595
	tristate "SiS 5595"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the 
	  SiS5595 SMBus (a subset of I2C) interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-sis5595.

config I2C_SIS630
	tristate "SiS 630/730"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the 
	  SiS630 and SiS730 SMBus (a subset of I2C) interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-sis630.

config I2C_SIS96X
	tristate "SiS 96x"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the SiS
	  96x SMBus (a subset of I2C) interfaces.  Specifically, the following
	  chipsets are supported:
	    645/961
	    645DX/961
	    645DX/962
	    648/961
	    650/961
	    735
	    745

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-sis96x.

config I2C_STUB
	tristate "I2C/SMBus Test Stub"
	depends on I2C && EXPERIMENTAL && 'm'
	default 'n'
	help
	  This module may be useful to developers of SMBus client drivers,
	  especially for certain kinds of sensor chips.

	  If you do build this module, be sure to read the notes and warnings
	  in <file:Documentation/i2c/i2c-stub>.

	  If you don't know what to do here, definitely say N.

config I2C_VIA
	tristate "VIA 82C586B"
	depends on I2C && PCI && EXPERIMENTAL
	select I2C_ALGOBIT
	help
	  If you say yes to this option, support will be included for the VIA
          82C586B I2C interface

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-via.

config I2C_VIAPRO
	tristate "VIA 82C596/82C686/823x"
	depends on I2C && PCI
	help
	  If you say yes to this option, support will be included for the VIA
	  82C596/82C686/823x I2C interfaces.  Specifically, the following 
	  chipsets are supported:
	  82C596A/B
	  82C686A/B
	  8231
	  8233
	  8233A
	  8235
	  8237

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-viapro.

config I2C_VOODOO3
	tristate "Voodoo 3"
	depends on I2C && PCI
	select I2C_ALGOBIT
	help
	  If you say yes to this option, support will be included for the
	  Voodoo 3 I2C interface.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-voodoo3.

config I2C_PCA_ISA
	tristate "PCA9564 on an ISA bus"
	depends on I2C
	select I2C_ALGOPCA
	help
	  This driver supports ISA boards using the Philips PCA 9564
	  Parallel bus to I2C bus controller
	  
	  This driver can also be built as a module.  If so, the module
	  will be called i2c-pca-isa.

config I2C_MV64XXX
	tristate "Marvell mv64xxx I2C Controller"
	depends on I2C && MV64X60 && EXPERIMENTAL
	help
	  If you say yes to this option, support will be included for the
	  built-in I2C interface on the Marvell 64xxx line of host bridges.

	  This driver can also be built as a module.  If so, the module
	  will be called i2c-mv64xxx.

endmenu
Commit	Line	Data
1da177e4 LT	1	#
	2	# Sensor device configuration
	3	#
	4
	5	menu "I2C Hardware Bus support"
	6	depends on I2C
	7
	8	config I2C_ALI1535
	9	tristate "ALI 1535"
5d740fe9	10	depends on I2C && PCI
1da177e4 LT	11	help
	12	If you say yes to this option, support will be included for the SMB
	13	Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
	14	controller is part of the 7101 device, which is an ACPI-compliant
	15	Power Management Unit (PMU).
	16
	17	This driver can also be built as a module. If so, the module
	18	will be called i2c-ali1535.
	19
	20	config I2C_ALI1563
	21	tristate "ALI 1563"
	22	depends on I2C && PCI && EXPERIMENTAL
	23	help
	24	If you say yes to this option, support will be included for the SMB
	25	Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
	26	controller is part of the 7101 device, which is an ACPI-compliant
	27	Power Management Unit (PMU).
	28
	29	This driver can also be built as a module. If so, the module
	30	will be called i2c-ali1563.
	31
	32	config I2C_ALI15X3
	33	tristate "ALI 15x3"
5d740fe9	34	depends on I2C && PCI
1da177e4 LT	35	help
	36	If you say yes to this option, support will be included for the
	37	Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
	38
	39	This driver can also be built as a module. If so, the module
	40	will be called i2c-ali15x3.
	41
	42	config I2C_AMD756
	43	tristate "AMD 756/766/768/8111 and nVidia nForce"
5d740fe9	44	depends on I2C && PCI
1da177e4 LT	45	help
	46	If you say yes to this option, support will be included for the AMD
	47	756/766/768 mainboard I2C interfaces. The driver also includes
	48	support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
	49	the nVidia nForce I2C interface.
	50
	51	This driver can also be built as a module. If so, the module
	52	will be called i2c-amd756.
	53
	54	config I2C_AMD756_S4882
	55	tristate "SMBus multiplexing on the Tyan S4882"
	56	depends on I2C_AMD756 && EXPERIMENTAL
	57	help
	58	Enabling this option will add specific SMBus support for the Tyan
	59	S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
	60	over 8 different channels, where the various memory module EEPROMs
	61	and temperature sensors live. Saying yes here will give you access
	62	to these in addition to the trunk.
	63
	64	This driver can also be built as a module. If so, the module
	65	will be called i2c-amd756-s4882.
	66
	67	config I2C_AMD8111
	68	tristate "AMD 8111"
5d740fe9	69	depends on I2C && PCI
1da177e4 LT	70	help
	71	If you say yes to this option, support will be included for the
	72	second (SMBus 2.0) AMD 8111 mainboard I2C interface.
	73
	74	This driver can also be built as a module. If so, the module
	75	will be called i2c-amd8111.
	76
	77	config I2C_AU1550
	78	tristate "Au1550 SMBus interface"
	79	depends on I2C && SOC_AU1550
	80	help
	81	If you say yes to this option, support will be included for the
	82	Au1550 SMBus interface.
	83
	84	This driver can also be built as a module. If so, the module
	85	will be called i2c-au1550.
	86
	87	config I2C_ELEKTOR
	88	tristate "Elektor ISA card"
	89	depends on I2C && ISA && BROKEN_ON_SMP
	90	select I2C_ALGOPCF
	91	help
	92	This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
	93	such an adapter.
	94
	95	This support is also available as a module. If so, the module
	96	will be called i2c-elektor.
	97
	98	config I2C_HYDRA
	99	tristate "CHRP Apple Hydra Mac I/O I2C interface"
	100	depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
	101	select I2C_ALGOBIT
	102	help
	103	This supports the use of the I2C interface in the Apple Hydra Mac
	104	I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
	105	have such a machine.
	106
	107	This support is also available as a module. If so, the module
	108	will be called i2c-hydra.
	109
	110	config I2C_I801
	111	tristate "Intel 82801 (ICH)"
5d740fe9	112	depends on I2C && PCI
1da177e4 LT	113	help
	114	If you say yes to this option, support will be included for the Intel
	115	801 family of mainboard I2C interfaces. Specifically, the following
	116	versions of the chipset are supported:
	117	82801AA
	118	82801AB
	119	82801BA
	120	82801CA/CAM
	121	82801DB
	122	82801EB/ER (ICH5/ICH5R)
	123	6300ESB
	124	ICH6
	125	ICH7
b0a70b57	126	ESB2
8254fc4a	127	ICH8
1da177e4 LT	128
	129	This driver can also be built as a module. If so, the module
	130	will be called i2c-i801.
	131
	132	config I2C_I810
	133	tristate "Intel 810/815"
5d740fe9	134	depends on I2C && PCI
1da177e4 LT	135	select I2C_ALGOBIT
	136	help
	137	If you say yes to this option, support will be included for the Intel
	138	810/815 family of mainboard I2C interfaces. Specifically, the
142078f6	139	following versions of the chipset are supported:
1da177e4 LT	140	i810AA
	141	i810AB
	142	i810E
	143	i815
142078f6	144	i845G
1da177e4 LT	145
	146	This driver can also be built as a module. If so, the module
	147	will be called i2c-i810.
	148
b652b438 RK	149	config I2C_PXA
	150	tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
	151	depends on I2C && EXPERIMENTAL && ARCH_PXA
	152	help
	153	If you have devices in the PXA I2C bus, say yes to this option.
	154	This driver can also be built as a module. If so, the module
	155	will be called i2c-pxa.
	156
	157	config I2C_PXA_SLAVE
	158	bool "Intel PXA2XX I2C Slave comms support"
	159	depends on I2C_PXA
	160	help
	161	Support I2C slave mode communications on the PXA I2C bus. This
	162	is necessary for systems where the PXA may be a target on the
	163	I2C bus.
	164
1da177e4 LT	165	config I2C_PIIX4
	166	tristate "Intel PIIX4"
	167	depends on I2C && PCI
	168	help
	169	If you say yes to this option, support will be included for the Intel
	170	PIIX4 family of mainboard I2C interfaces. Specifically, the following
5f7ea3c5 MD	171	versions of the chipset are supported (note that Serverworks is part
5f7ea3c5 MD	172	of Broadcom):
1da177e4 LT	173	Intel PIIX4
	174	Intel 440MX
	175	Serverworks OSB4
	176	Serverworks CSB5
	177	Serverworks CSB6
5f7ea3c5	178	Serverworks HT-1000
1da177e4 LT	179	SMSC Victory66
	180
	181	This driver can also be built as a module. If so, the module
	182	will be called i2c-piix4.
	183
	184	config I2C_IBM_IIC
	185	tristate "IBM PPC 4xx on-chip I2C interface"
	186	depends on IBM_OCP && I2C
	187	help
	188	Say Y here if you want to use IIC peripheral found on
	189	embedded IBM PPC 4xx based systems.
	190
	191	This driver can also be built as a module. If so, the module
	192	will be called i2c-ibm_iic.
	193
	194	config I2C_IOP3XX
	195	tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
	196	depends on (ARCH_IOP3XX \|\| ARCH_IXP4XX) && I2C
	197	help
	198	Say Y here if you want to use the IIC bus controller on
	199	the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
	200
	201	This driver can also be built as a module. If so, the module
	202	will be called i2c-iop3xx.
	203
	204	config I2C_ISA
5042c7d7	205	tristate
5d740fe9	206	depends on I2C
1da177e4 LT	207
	208	config I2C_ITE
	209	tristate "ITE I2C Adapter"
	210	depends on I2C && MIPS_ITE8172
	211	select I2C_ALGOITE
	212	help
	213	This supports the ITE8172 I2C peripheral found on some MIPS
	214	systems. Say Y if you have one of these. You should also say Y for
	215	the ITE I2C driver algorithm support above.
	216
	217	This support is also available as a module. If so, the module
	218	will be called i2c-ite.
	219
	220	config I2C_IXP4XX
	221	tristate "IXP4xx GPIO-Based I2C Interface"
	222	depends on I2C && ARCH_IXP4XX
	223	select I2C_ALGOBIT
	224	help
	225	Say Y here if you have an Intel IXP4xx(420,421,422,425) based
	226	system and are using GPIO lines for an I2C bus.
	227
	228	This support is also available as a module. If so, the module
	229	will be called i2c-ixp4xx.
	230
	231	config I2C_IXP2000
	232	tristate "IXP2000 GPIO-Based I2C Interface"
	233	depends on I2C && ARCH_IXP2000
	234	select I2C_ALGOBIT
	235	help
	236	Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
	237	system and are using GPIO lines for an I2C bus.
	238
	239	This support is also available as a module. If so, the module
	240	will be called i2c-ixp2000.
	241
a28d3af2 BH	242	config I2C_POWERMAC
a28d3af2 BH	243	tristate "Powermac I2C interface"
1da177e4	244	depends on I2C && PPC_PMAC
a28d3af2	245	default y
1da177e4	246	help
a28d3af2 BH	247	This exposes the various PowerMac i2c interfaces to the linux i2c
	248	layer and to userland. It is used by various drivers on the powemac
	249	platform, thus should generally be enabled.
0365ba7f BH	250
0365ba7f BH	251	This support is also available as a module. If so, the module
a28d3af2	252	will be called i2c-powermac.
0365ba7f	253
1da177e4 LT	254	config I2C_MPC
1da177e4 LT	255	tristate "MPC107/824x/85xx/52xx"
b5a48dad	256	depends on I2C && PPC32
1da177e4 LT	257	help
	258	If you say yes to this option, support will be included for the
	259	built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
	260	MPC85xx family processors. The driver may also work on 52xx
	261	family processors, though interrupts are known not to work.
	262
	263	This driver can also be built as a module. If so, the module
	264	will be called i2c-mpc.
	265
	266	config I2C_NFORCE2
5d740fe9 M	267	tristate "Nvidia nForce2, nForce3 and nForce4"
5d740fe9 M	268	depends on I2C && PCI
1da177e4 LT	269	help
1da177e4 LT	270	If you say yes to this option, support will be included for the Nvidia
5d740fe9	271	nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
1da177e4 LT	272
	273	This driver can also be built as a module. If so, the module
	274	will be called i2c-nforce2.
	275
	276	config I2C_PARPORT
	277	tristate "Parallel port adapter"
	278	depends on I2C && PARPORT
	279	select I2C_ALGOBIT
	280	help
	281	This supports parallel port I2C adapters such as the ones made by
	282	Philips or Velleman, Analog Devices evaluation boards, and more.
	283	Basically any adapter using the parallel port as an I2C bus with
	284	no extra chipset is supported by this driver, or could be.
	285
	286	This driver is a replacement for (and was inspired by) an older
	287	driver named i2c-philips-par. The new driver supports more devices,
	288	and makes it easier to add support for new devices.
e97b81dd MH	289
	290	An adapter type parameter is now mandatory. Please read the file
	291	Documentation/i2c/busses/i2c-parport for details.
	292
1da177e4 LT	293	Another driver exists, named i2c-parport-light, which doesn't depend
	294	on the parport driver. This is meant for embedded systems. Don't say
	295	Y here if you intend to say Y or M there.
	296
	297	This support is also available as a module. If so, the module
	298	will be called i2c-parport.
	299
	300	config I2C_PARPORT_LIGHT
	301	tristate "Parallel port adapter (light)"
	302	depends on I2C
	303	select I2C_ALGOBIT
	304	help
	305	This supports parallel port I2C adapters such as the ones made by
	306	Philips or Velleman, Analog Devices evaluation boards, and more.
	307	Basically any adapter using the parallel port as an I2C bus with
	308	no extra chipset is supported by this driver, or could be.
	309
	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 prefered 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	dasiy-chain other parallel port devices.
	316
	317	Don't say Y here if you said Y or M to i2c-parport. Saying M to
	318	both is possible but both modules should not be loaded at the same
	319	time.
	320
	321	This support is also available as a module. If so, the module
	322	will be called i2c-parport-light.
	323
	324	config I2C_PROSAVAGE
	325	tristate "S3/VIA (Pro)Savage"
5d740fe9	326	depends on I2C && PCI
1da177e4 LT	327	select I2C_ALGOBIT
	328	help
	329	If you say yes to this option, support will be included for the
	330	I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
	331	graphics processors.
	332	chipsets supported:
	333	S3/VIA KM266/VT8375 aka ProSavage8
	334	S3/VIA KM133/VT8365 aka Savage4
	335
	336	This support is also available as a module. If so, the module
	337	will be called i2c-prosavage.
	338
	339	config I2C_RPXLITE
	340	tristate "Embedded Planet RPX Lite/Classic support"
	341	depends on (RPXLITE \|\| RPXCLASSIC) && I2C
	342	select I2C_ALGO8XX
	343
	344	config I2C_S3C2410
	345	tristate "S3C2410 I2C Driver"
	346	depends on I2C && ARCH_S3C2410
	347	help
	348	Say Y here to include support for I2C controller in the
	349	Samsung S3C2410 based System-on-Chip devices.
	350
	351	config I2C_SAVAGE4
	352	tristate "S3 Savage 4"
	353	depends on I2C && PCI && EXPERIMENTAL
	354	select I2C_ALGOBIT
	355	help
	356	If you say yes to this option, support will be included for the
	357	S3 Savage 4 I2C interface.
	358
	359	This driver can also be built as a module. If so, the module
	360	will be called i2c-savage4.
	361
	362	config I2C_SIBYTE
	363	tristate "SiByte SMBus interface"
	364	depends on SIBYTE_SB1xxx_SOC && I2C
	365	help
	366	Supports the SiByte SOC on-chip I2C interfaces (2 channels).
	367
	368	config SCx200_I2C
	369	tristate "NatSemi SCx200 I2C using GPIO pins"
	370	depends on SCx200_GPIO && I2C
	371	select I2C_ALGOBIT
	372	help
	373	Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
	374
	375	If you don't know what to do here, say N.
	376
	377	This support is also available as a module. If so, the module
	378	will be called scx200_i2c.
	379
	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
	388	config SCx200_I2C_SDA
	389	int "GPIO pin used for SDA"
	390	depends on SCx200_I2C
391	default "13"
392	help
393	Enter the GPIO pin number used for the SSA signal. This value can
394	also be specified with a module parameter.
395
396	config SCx200_ACB
a417bbd3	397	tristate "Geode ACCESS.bus support"
cdf263f1	398	depends on X86_32 && I2C && PCI
1da177e4	399	help
a417bbd3 BG	400	Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
a417bbd3 BG	401	SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1da177e4 LT	402
	403	If you don't know what to do here, say N.
	404
	405	This support is also available as a module. If so, the module
	406	will be called scx200_acb.
	407
	408	config I2C_SIS5595
	409	tristate "SiS 5595"
5d740fe9	410	depends on I2C && PCI
1da177e4 LT	411	help
	412	If you say yes to this option, support will be included for the
	413	SiS5595 SMBus (a subset of I2C) interface.
	414
	415	This driver can also be built as a module. If so, the module
	416	will be called i2c-sis5595.
	417
	418	config I2C_SIS630
	419	tristate "SiS 630/730"
5d740fe9	420	depends on I2C && PCI
1da177e4 LT	421	help
	422	If you say yes to this option, support will be included for the
	423	SiS630 and SiS730 SMBus (a subset of I2C) interface.
	424
	425	This driver can also be built as a module. If so, the module
	426	will be called i2c-sis630.
	427
	428	config I2C_SIS96X
	429	tristate "SiS 96x"
5d740fe9	430	depends on I2C && PCI
1da177e4 LT	431	help
	432	If you say yes to this option, support will be included for the SiS
	433	96x SMBus (a subset of I2C) interfaces. Specifically, the following
	434	chipsets are supported:
	435	645/961
	436	645DX/961
	437	645DX/962
	438	648/961
	439	650/961
	440	735
5d740fe9	441	745
1da177e4 LT	442
	443	This driver can also be built as a module. If so, the module
	444	will be called i2c-sis96x.
	445
	446	config I2C_STUB
	447	tristate "I2C/SMBus Test Stub"
	448	depends on I2C && EXPERIMENTAL && 'm'
	449	default 'n'
	450	help
	451	This module may be useful to developers of SMBus client drivers,
	452	especially for certain kinds of sensor chips.
	453
	454	If you do build this module, be sure to read the notes and warnings
	455	in <file:Documentation/i2c/i2c-stub>.
	456
	457	If you don't know what to do here, definitely say N.
	458
	459	config I2C_VIA
	460	tristate "VIA 82C586B"
	461	depends on I2C && PCI && EXPERIMENTAL
	462	select I2C_ALGOBIT
	463	help
	464	If you say yes to this option, support will be included for the VIA
	465	82C586B I2C interface
	466
	467	This driver can also be built as a module. If so, the module
	468	will be called i2c-via.
	469
	470	config I2C_VIAPRO
	471	tristate "VIA 82C596/82C686/823x"
5d740fe9	472	depends on I2C && PCI
1da177e4 LT	473	help
	474	If you say yes to this option, support will be included for the VIA
	475	82C596/82C686/823x I2C interfaces. Specifically, the following
	476	chipsets are supported:
	477	82C596A/B
	478	82C686A/B
	479	8231
	480	8233
	481	8233A
	482	8235
	483	8237
	484
	485	This driver can also be built as a module. If so, the module
	486	will be called i2c-viapro.
	487
	488	config I2C_VOODOO3
	489	tristate "Voodoo 3"
5d740fe9	490	depends on I2C && PCI
1da177e4 LT	491	select I2C_ALGOBIT
	492	help
	493	If you say yes to this option, support will be included for the
	494	Voodoo 3 I2C interface.
	495
	496	This driver can also be built as a module. If so, the module
	497	will be called i2c-voodoo3.
	498
	499	config I2C_PCA_ISA
	500	tristate "PCA9564 on an ISA bus"
	501	depends on I2C
	502	select I2C_ALGOPCA
	503	help
	504	This driver supports ISA boards using the Philips PCA 9564
	505	Parallel bus to I2C bus controller
	506
	507	This driver can also be built as a module. If so, the module
	508	will be called i2c-pca-isa.
	509
	510	config I2C_MV64XXX
	511	tristate "Marvell mv64xxx I2C Controller"
	512	depends on I2C && MV64X60 && EXPERIMENTAL
	513	help
	514	If you say yes to this option, support will be included for the
	515	built-in I2C interface on the Marvell 64xxx line of host bridges.
	516
	517	This driver can also be built as a module. If so, the module
	518	will be called i2c-mv64xxx.
	519
	520	endmenu