Searched +full:eeprom +full:- +full:93 +full:xx46 (Results 1 – 3 of 3) sorted by relevance
/linux/Documentation/devicetree/bindings/eeprom/ |
H A D | microchip,93lc46b.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/eeprom/microchip,93lc46b.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Microchip 93xx46 SPI compatible EEPROM family 10 - Cory Tusar <cory.tusar@pid1solutions.com> 15 - atmel,at93c46 16 - atmel,at93c46d 17 - atmel,at93c56 18 - atmel,at93c66 [all …]
|
/linux/drivers/misc/eeprom/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 2 menu "EEPROM support" 15 board. Use these generic chip names, instead of vendor-specific 24 as read-only won't help recover from this. Also, if your chip 25 has any software write-protect mechanism you may want to review the 44 after you configure the board init code to know about each eeprom 54 If you say yes here you get read-only support for the user EEPROM of 55 the Maxim MAX6874/5 EEPROM-programmable, quad power-supply 58 All other features of this chip should be accessed via i2c-dev. 65 tristate "EEPROM 93CX6 support" [all …]
|
H A D | digsy_mtc_eeprom.c | 1 // SPDX-License-Identifier: GPL-2.0-only 8 * FIXME: this driver is used on a device-tree probed platform: it 9 * should be defined as a bit-banged SPI device and probed from the device 13 * Add proper SPI and EEPROM in arch/powerpc/boot/dts/digsy_mtc.dts 32 PROPERTY_ENTRY_U32("data-size", 8), 71 .modalias = "eeprom-93xx46",
|