i2c: Remove 3 deprecated bus drivers (20a9b6e7) · Commits · e / devices / android_kernel_fairphone_FP3

Documentation/feature-removal-schedule.txt

+0 −7

Original line number	Diff line number	Diff line
		@@ -222,13 +222,6 @@ Who: Thomas Gleixner <tglx@linutronix.de>

		---------------------------

		What: i2c-i810, i2c-prosavage and i2c-savage4
		When: May 2008
		Why: These drivers are superseded by i810fb, intelfb and savagefb.
		Who: Jean Delvare <khali@linux-fr.org>

		---------------------------

		What (Why):
		- include/linux/netfilter_ipv4/ipt_TOS.h ipt_tos.h header files
		(superseded by xt_TOS/xt_tos target & match)

Documentation/i2c/busses/i2c-i810

deleted100644 → 0

+0 −47

Original line number	Diff line number	Diff line
		Kernel driver i2c-i810

		Supported adapters:
		* Intel 82810, 82810-DC100, 82810E, and 82815 (GMCH)
		* Intel 82845G (GMCH)

		Authors:
		Frodo Looijaard <frodol@dds.nl>,
		Philip Edelbrock <phil@netroedge.com>,
		Kyösti Mälkki <kmalkki@cc.hut.fi>,
		Ralph Metzler <rjkm@thp.uni-koeln.de>,
		Mark D. Studebaker <mdsxyz123@yahoo.com>

		Main contact: Mark Studebaker <mdsxyz123@yahoo.com>

		Description
		-----------

		WARNING: If you have an '810' or '815' motherboard, your standard I2C
		temperature sensors are most likely on the 801's I2C bus. You want the
		i2c-i801 driver for those, not this driver.

		Now for the i2c-i810...

		The GMCH chip contains two I2C interfaces.

		The first interface is used for DDC (Data Display Channel) which is a
		serial channel through the VGA monitor connector to a DDC-compliant
		monitor. This interface is defined by the Video Electronics Standards
		Association (VESA). The standards are available for purchase at
		http://www.vesa.org .

		The second interface is a general-purpose I2C bus. It may be connected to a
		TV-out chip such as the BT869 or possibly to a digital flat-panel display.

		Features
		--------

		Both busses use the i2c-algo-bit driver for 'bit banging'
		and support for specific transactions is provided by i2c-algo-bit.

		Issues
		------

		If you enable bus testing in i2c-algo-bit (insmod i2c-algo-bit bit_test=1),
		the test may fail; if so, the i2c-i810 driver won't be inserted. However,
		we think this has been fixed.

Documentation/i2c/busses/i2c-prosavage

deleted100644 → 0

+0 −23

Original line number	Diff line number	Diff line
		Kernel driver i2c-prosavage

		Supported adapters:

		S3/VIA KM266/VT8375 aka ProSavage8
		S3/VIA KM133/VT8365 aka Savage4

		Author: Henk Vergonet <henk@god.dyndns.org>

		Description
		-----------

		The Savage4 chips contain two I2C interfaces (aka a I2C 'master' or
		'host').

		The first interface is used for DDC (Data Display Channel) which is a
		serial channel through the VGA monitor connector to a DDC-compliant
		monitor. This interface is defined by the Video Electronics Standards
		Association (VESA). The standards are available for purchase at
		http://www.vesa.org . The second interface is a general-purpose I2C bus.

		Usefull for gaining access to the TV Encoder chips.

Documentation/i2c/busses/i2c-savage4

deleted100644 → 0

+0 −26

Original line number	Diff line number	Diff line
		Kernel driver i2c-savage4

		Supported adapters:
		* Savage4
		* Savage2000

		Authors:
		Alexander Wold <awold@bigfoot.com>,
		Mark D. Studebaker <mdsxyz123@yahoo.com>

		Description
		-----------

		The Savage4 chips contain two I2C interfaces (aka a I2C 'master'
		or 'host').

		The first interface is used for DDC (Data Display Channel) which is a
		serial channel through the VGA monitor connector to a DDC-compliant
		monitor. This interface is defined by the Video Electronics Standards
		Association (VESA). The standards are available for purchase at
		http://www.vesa.org . The DDC bus is not yet supported because its register
		is not directly memory-mapped.

		The second interface is a general-purpose I2C bus. This is the only
		interface supported by the driver at the moment.

drivers/i2c/busses/Kconfig

+0 −52

Original line number	Diff line number	Diff line
		@@ -186,26 +186,6 @@ config I2C_I801
		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 (DEPRECATED)"
		default n
		depends on 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 is deprecated in favor of the i810fb and intelfb drivers.

		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 EXPERIMENTAL && ARCH_PXA
		@@ -402,24 +382,6 @@ config I2C_PASEMI
		help
		Supports the PA Semi PWRficient on-chip SMBus interfaces.

		config I2C_PROSAVAGE
		tristate "S3/VIA (Pro)Savage (DEPRECATED)"
		default n
		depends on 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 driver is deprecated in favor of the savagefb driver.

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

		config I2C_S3C2410
		tristate "S3C2410 I2C Driver"
		depends on ARCH_S3C2410
		@@ -427,20 +389,6 @@ config I2C_S3C2410
		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 (DEPRECATED)"
		default n
		depends on PCI
		select I2C_ALGOBIT
		help
		If you say yes to this option, support will be included for the
		S3 Savage 4 I2C interface.

		This driver is deprecated in favor of the savagefb driver.

		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