Home
last modified time | relevance | path

Searched +full:eeprom +full:- +full:93 +full:xx46 (Results 1 – 10 of 10) sorted by relevance

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/eeprom/
Dmicrochip,93lc46b.yaml1 # 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/
Deeprom-93xx46.txt1 EEPROMs (SPI) compatible with Microchip Technology 93xx46 family.
4 - compatible : shall be one of:
6 "eeprom-93xx46"
7 - data-size : number of data bits per word (either 8 or 16)
10 - read-only : parameter-less property which disables writes to the EEPROM
11 - select-gpios : if present, specifies the GPIO that will be asserted prior to
12 each access to the EEPROM (e.g. for SPI bus multiplexing)
14 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
15 apply. In particular, "reg" and "spi-max-frequency" properties must be given.
18 eeprom@0 {
[all …]
/kernel/linux/linux-6.6/drivers/misc/eeprom/
DKconfig1 # 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
43 after you configure the board init code to know about each eeprom
50 tristate "Old I2C EEPROM reader (DEPRECATED)"
53 If you say yes here you get read-only access to the EEPROM data
61 will be called eeprom.
67 If you say yes here you get read-only support for the user EEPROM of
[all …]
Deeprom_93xx46.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Driver for 93xx46 EEPROMs
20 #include <linux/nvmem-provider.h>
70 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_SINGLE_WORD_READ; in has_quirk_single_word_read()
75 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_INSTRUCTION_LENGTH; in has_quirk_instruction_length()
80 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_EXTRA_READ_CYCLE; in has_quirk_extra_read_cycle()
91 if (unlikely(off >= edev->size)) in eeprom_93xx46_read()
93 if ((off + count) > edev->size) in eeprom_93xx46_read()
94 count = edev->size - off; in eeprom_93xx46_read()
98 mutex_lock(&edev->lock); in eeprom_93xx46_read()
[all …]
Ddigsy_mtc_eeprom.c1 // 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
79 .modalias = "93xx46",
93 "93xx46 EEPROMs OE"); in digsy_mtc_eeprom_devices_init()
/kernel/linux/linux-5.10/drivers/misc/eeprom/
DKconfig1 # 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
42 after you configure the board init code to know about each eeprom
49 tristate "Old I2C EEPROM reader (DEPRECATED)"
52 If you say yes here you get read-only access to the EEPROM data
60 will be called eeprom.
66 If you say yes here you get read-only support for the user EEPROM of
[all …]
Deeprom_93xx46.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Driver for 93xx46 EEPROMs
19 #include <linux/nvmem-provider.h>
54 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_SINGLE_WORD_READ; in has_quirk_single_word_read()
59 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_INSTRUCTION_LENGTH; in has_quirk_instruction_length()
64 return edev->pdata->quirks & EEPROM_93XX46_QUIRK_EXTRA_READ_CYCLE; in has_quirk_extra_read_cycle()
74 if (unlikely(off >= edev->size)) in eeprom_93xx46_read()
76 if ((off + count) > edev->size) in eeprom_93xx46_read()
77 count = edev->size - off; in eeprom_93xx46_read()
81 mutex_lock(&edev->lock); in eeprom_93xx46_read()
[all …]
Ddigsy_mtc_eeprom.c1 // 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
79 .modalias = "93xx46",
93 "93xx46 EEPROMs OE"); in digsy_mtc_eeprom_devices_init()
/kernel/linux/linux-6.6/arch/arm/boot/dts/nxp/imx/
Dimx51-zii-rdu1.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
6 /dts-v1/;
8 #include <dt-bindings/sound/fsl-imx-audmux.h>
12 compatible = "zii,imx51-rdu1", "fsl,imx51";
15 stdout-path = &uart1;
25 mdio-gpio0 = &mdio_gpio;
30 compatible = "fixed-clock";
31 #clock-cells = <0>;
32 clock-frequency = <26000000>;
36 compatible = "gpio-gate-clock";
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dimx51-zii-rdu1.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
6 /dts-v1/;
8 #include <dt-bindings/sound/fsl-imx-audmux.h>
12 compatible = "zii,imx51-rdu1", "fsl,imx51";
15 stdout-path = &uart1;
25 mdio-gpio0 = &mdio_gpio;
30 compatible = "fixed-clock";
31 #clock-cells = <0>;
32 clock-frequency = <26000000>;
36 compatible = "gpio-gate-clock";
[all …]