Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5195e509 authored by Wolfram Sang's avatar Wolfram Sang Committed by Jean Delvare
Browse files

i2c: Move at24 to drivers/misc/eeprom



As drivers/i2c/chips is going to go away, move the driver to
drivers/misc/eeprom. Other eeprom drivers may be moved here later, too.
Update Kconfig text to specify this driver as I2C.

Signed-off-by: default avatarWolfram Sang <w.sang@pengutronix.de>
Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
parent a01064a9
Loading
Loading
Loading
Loading
+0 −26
Original line number Diff line number Diff line
@@ -16,32 +16,6 @@ config DS1682
	  This driver can also be built as a module.  If so, the module
	  will be called ds1682.

config AT24
	tristate "EEPROMs from most vendors"
	depends on SYSFS && EXPERIMENTAL
	help
	  Enable this driver to get read/write support to most I2C EEPROMs,
	  after you configure the driver to know about each EEPROM on
	  your target board.  Use these generic chip names, instead of
	  vendor-specific ones like at24c64 or 24lc02:

	     24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
	     24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024

	  Unless you like data loss puzzles, always be sure that any chip
	  you configure as a 24c32 (32 kbit) or larger is NOT really a
	  24c16 (16 kbit) or smaller, and vice versa. Marking the chip
	  as read-only won't help recover from this. Also, if your chip
	  has any software write-protect mechanism you may want to review the
	  code to make sure this driver won't turn it on by accident.

	  If you use this with an SMBus adapter instead of an I2C adapter,
	  full functionality is not available.  Only smaller devices are
	  supported (24c16 and below, max 4 kByte).

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

config SENSORS_EEPROM
	tristate "EEPROM reader"
	depends on EXPERIMENTAL
+0 −1
Original line number Diff line number Diff line
@@ -11,7 +11,6 @@
#

obj-$(CONFIG_DS1682)		+= ds1682.o
obj-$(CONFIG_AT24)		+= at24.o
obj-$(CONFIG_SENSORS_EEPROM)	+= eeprom.o
obj-$(CONFIG_SENSORS_MAX6875)	+= max6875.o
obj-$(CONFIG_SENSORS_PCA9539)	+= pca9539.o
+1 −0
Original line number Diff line number Diff line
@@ -231,5 +231,6 @@ config DELL_LAPTOP
	laptops.

source "drivers/misc/c2port/Kconfig"
source "drivers/misc/eeprom/Kconfig"

endif # MISC_DEVICES
+1 −0
Original line number Diff line number Diff line
@@ -20,3 +20,4 @@ obj-$(CONFIG_SGI_XP) += sgi-xp/
obj-$(CONFIG_SGI_GRU)		+= sgi-gru/
obj-$(CONFIG_HP_ILO)		+= hpilo.o
obj-$(CONFIG_C2PORT)		+= c2port/
obj-y				+= eeprom/
+29 −0
Original line number Diff line number Diff line
menu "EEPROM support"

config AT24
	tristate "I2C EEPROMs from most vendors"
	depends on I2C && SYSFS && EXPERIMENTAL
	help
	  Enable this driver to get read/write support to most I2C EEPROMs,
	  after you configure the driver to know about each EEPROM on
	  your target board.  Use these generic chip names, instead of
	  vendor-specific ones like at24c64 or 24lc02:

	     24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
	     24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024

	  Unless you like data loss puzzles, always be sure that any chip
	  you configure as a 24c32 (32 kbit) or larger is NOT really a
	  24c16 (16 kbit) or smaller, and vice versa. Marking the chip
	  as read-only won't help recover from this. Also, if your chip
	  has any software write-protect mechanism you may want to review the
	  code to make sure this driver won't turn it on by accident.

	  If you use this with an SMBus adapter instead of an I2C adapter,
	  full functionality is not available.  Only smaller devices are
	  supported (24c16 and below, max 4 kByte).

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

endmenu
Loading