Home
last modified time | relevance | path

Searched refs:OTP (Results 1 – 25 of 29) sorted by relevance

12

/linux-6.12.1/drivers/nvmem/
DKconfig44 tristate "Broadcom On-Chip OTP Controller support"
49 Say y here to enable read/write access to the Broadcom OTP
76 tristate "i.MX 6/7/8 On-Chip OTP Controller support"
80 This is a driver for the On-Chip OTP Controller (OCOTP) available on
88 tristate "i.MX On-Chip OTP Controller support"
93 This is a driver for the On-Chip OTP Controller (OCOTP)
97 tristate "i.MX8 SCU On-Chip OTP Controller support"
101 This is a driver for the SCU On-Chip OTP Controller (OCOTP)
117 tristate "Microchip LAN9662 OTP controller support"
121 This driver enables the OTP controller available on Microchip LAN9662
[all …]
/linux-6.12.1/drivers/mtd/nand/onenand/
DKconfig45 bool "OneNAND OTP Support"
49 Also, 1st Block of NAND Flash Array can be used as OTP.
51 The OTP block can be read, programmed and locked using the same
53 OTP block cannot be erased.
55 OTP block is fully-guaranteed to be a valid block.
/linux-6.12.1/Documentation/devicetree/bindings/nvmem/
Dvf610-ocotp.txt1 On-Chip OTP Memory for Freescale Vybrid
8 reg : Address and length of OTP controller and fuse map registers
Dlpc1850-otp.txt1 * NXP LPC18xx OTP memory
3 Internal OTP (One Time Programmable) memory for NXP LPC18xx/43xx devices.
Dbrcm,ocotp.txt1 Broadcom OTP memory controller
8 - reg: Base address of the OTP controller.
/linux-6.12.1/Documentation/devicetree/bindings/regulator/
Dpalmas-pmic.txt3 The tps659038 for the AM57x class have OTP spins that
5 is not a need to add the OTP spins to the palmas driver. The
35 For ti,palmas-pmic - smps12, smps123, smps3 depending on OTP,
50 ti,smps-range - OTP has the wrong range set for the hardware so override
/linux-6.12.1/drivers/misc/mchp_pci1xxxx/
DKconfig2 tristate "Microchip PCI1XXXX PCIe to GPIO Expander + OTP/EEPROM manager"
11 which also has registers to interface with the OTP and EEPROM.
/linux-6.12.1/Documentation/devicetree/bindings/net/
Dmicrochip,lan78xx.txt3 The LAN78XX devices are usually configured by programming their OTP or with
5 The Device Tree properties, if present, override the OTP and EEPROM.
/linux-6.12.1/Documentation/hwmon/
Dsht15.rst48 The humidity calibration coefficients are programmed into an OTP memory on the
67 flag to indicate not to reload from OTP (default to false).
Dmpq8785.rst34 over-temperature protection (OTP).
/linux-6.12.1/Documentation/ABI/testing/
Ddebugfs-turris-mox-rwtm9 device's OTP. The message must be exactly 64 bytes
Dsysfs-platform-silicom27 OTP status:
/linux-6.12.1/drivers/mtd/chips/
DKconfig156 bool "Protection Registers aka one-time programmable (OTP) bits"
166 programmable (OTP) bits; when programmed, register bits cannot be
173 because the Lock Register bits themselves are OTP, when programmed,
178 in the programming of OTP bits will waste them.
/linux-6.12.1/Documentation/devicetree/bindings/mfd/
Dpalmas.txt31 hardware, if not set will use muxing in OTP.
/linux-6.12.1/Documentation/w1/slaves/
Dw1_ds2406.rst15 These chips also provide 128 bytes of OTP EPROM, but reading/writing it is
/linux-6.12.1/Documentation/devicetree/bindings/input/
Dti,palmas-pwrbutton.txt18 NOTE: This depends on OTP support and POWERHOLD signal configuration
/linux-6.12.1/Documentation/ABI/stable/
Dsysfs-bus-nvmem48 "OTP", "Battery backed", "FRAM".
/linux-6.12.1/arch/arm/boot/dts/synaptics/
Dberlin2cd-valve-steamlink.dts42 * less depending on leakage value in OTP), and buck2 likely used for
/linux-6.12.1/arch/arm/boot/dts/nxp/imx/
Dimx6q-gk802.dts54 /* SDMC DM2016 1024 bit EEPROM + 128 bit OTP */
/linux-6.12.1/drivers/platform/cznic/
DKconfig47 able to program SOC's OTP on board revisions 32+,
/linux-6.12.1/drivers/mtd/devices/
DKconfig73 bool "DataFlash OTP support (Security Register)"
77 one-time-programmable (OTP) data. The first half may be written
/linux-6.12.1/arch/powerpc/boot/dts/
Dwii.dts227 * requires refactoring the PIC1, GPIO and OTP nodes
/linux-6.12.1/Documentation/security/keys/
Dtrusted-encrypted.rst47 Rooted to a one-time programmable key (OTP) that is generally burnt
49 DCP provides two keys that can be used as root of trust: the OTP key
51 the OTP key can be done via a module parameter (dcp_use_otp_key).
/linux-6.12.1/include/linux/mfd/
Didt8a340_reg.h458 #define OTP 0xcf70 macro
/linux-6.12.1/drivers/pmdomain/amlogic/
Dmeson-secure-pwrc.c125 SEC_PD(OTP, 0),

12