kernel/drivers/misc/eeprom/Kconfig, branch linux-4.16.y

eeprom: at24: add basic regmap_i2c support

2018-01-01T18:40:46Z

This patch adds basic regmap support to be used by subsequent patches of this series. Signed-off-by: Heiner Kallweit Signed-off-by: Bartosz Golaszewski

eeprom: Add IDT 89HPESx EEPROM/CSR driver

2017-01-19T10:39:57Z

This driver provides an access to EEPROM of IDT PCIe-switches. IDT PCIe- switches expose a simple SMBus interface to perform IO-operations from/to EEPROM, which is located at private (so called Master) SMBus. The driver creates a simple binary sysfs-file to have an access to the EEPROM using the SMBus-slave interface in the i2c-device susfs-directory: /sys/bus/i2c/devices/-/eeprom In case if read-only flag is specified at dts-node of the device, User-space applications won't be able to write to the EEPROM sysfs-node. Additionally IDT 89HPESx SMBus interface has an ability to read/write values of device CSRs. This driver exposes debugfs-file to perform simple IO-operations using that ability for just basic debug purpose. Particularly the next file is created in the specific debugfs-directory: /sys/kernel/debug/idt_csr/ Format of the debugfs-file value is: $ cat /sys/kernel/debug/idt_csr/-/; : So reading the content of the file gives current CSR address and it value. If User-space application wishes to change current CSR address, it can just write a proper value to the sysfs-file: $ echo "" > /sys/kernel/debug/idt_csr/-/ If it wants to change the CSR value as well, the format of the write operation is: $ echo ":" > \ /sys/kernel/debug/idt_csr/-/; CSR address and value can be any of hexadecimal, decimal or octal format. Signed-off-by: Serge Semin Signed-off-by: Greg Kroah-Hartman

eeprom: at25: remove nvmem regmap dependency

2016-05-01T21:01:00Z

This patch moves to nvmem support in the driver to use callback instead of regmap. Signed-off-by: Srinivas Kandagatla Signed-off-by: Greg Kroah-Hartman

eeprom: at24: remove nvmem regmap dependency

2016-05-01T21:01:00Z

This patch moves to nvmem support in the driver to use callback instead of regmap. Signed-off-by: Srinivas Kandagatla Signed-off-by: Greg Kroah-Hartman

eeprom: 93xx46: extend driver to plug into the NVMEM framework

2016-03-02T00:55:48Z

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backward compatibility in the NVMEM config structure, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla Signed-off-by: Greg Kroah-Hartman

eeprom: at25: extend driver to plug into the NVMEM framework

2016-03-02T00:55:48Z

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backwards compatibility in the NVMEM config, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla Signed-off-by: Greg Kroah-Hartman

eeprom: at24: extend driver to plug into the NVMEM framework

2016-03-02T00:55:48Z

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Set the NVMEM config structure to enable backward, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla Tested-by: Bartosz Golaszewski Signed-off-by: Greg Kroah-Hartman

nvmem: sunxi: Move the SID driver to the nvmem framework

2015-08-05T20:44:24Z

Now that we have the nvmem framework, we can consolidate the common driver code. Move the driver to the framework, and hopefully, it will fix the sysfs file creation race. Signed-off-by: Maxime Ripard [srinivas.kandagatla: Moved to regmap based EEPROM framework] Signed-off-by: Srinivas Kandagatla Tested-by: Philipp Zabel Tested-by: Rajendra Nayak Signed-off-by: Greg Kroah-Hartman

ARM: sunxi: Initial support for Allwinner's Security ID fuses

2013-09-26T20:47:36Z

Allwinner has electric fuses (efuse) on their line of chips. This driver reads those fuses, seeds the kernel entropy and exports them as a sysfs node. These fuses are most likely to be programmed at the factory, encoding things like Chip ID, some sort of serial number, etc. and appear to be reasonably unique. While in theory, these should be writeable by the user, it will probably be inconvenient to do so. Allwinner recommends that a certain input pin, labeled 'efuse_vddq', be connected to GND. To write these fuses however, a 2.5 V programming voltage needs to be applied to this pin. Even so, they can still be used to generate a board-unique mac from, board unique RSA key and seed the kernel RNG. On sun7i additional storage is available, this is initially used for an UEFI BOOT key, Secure JTAG key, HDMI-HDCP key and vendor specific keys. Currently supported are the following known chips: Allwinner sun4i (A10) Allwinner sun5i (A10s, A13) Allwinner sun7i (A20) Signed-off-by: Oliver Schinagl Acked-by: Maxime Ripard Signed-off-by: Greg Kroah-Hartman

drivers: misc: at24: mention other supported types in Kconfig

2013-01-28T04:26:41Z

As the at24 driver is able handle a bunch of serial storage chips other than EEPROMs this is now mentioned in Kconfig. Signed-off-by: Lars Poeschel Signed-off-by: Wolfram Sang