Commit | Line | Data |
---|---|---|
eace75cf SK |
1 | menuconfig NVMEM |
2 | tristate "NVMEM Support" | |
3 | select REGMAP | |
4 | help | |
5 | Support for NVMEM(Non Volatile Memory) devices like EEPROM, EFUSES... | |
6 | ||
7 | This framework is designed to provide a generic interface to NVMEM | |
8 | from both the Linux Kernel and the userspace. | |
9 | ||
10 | This driver can also be built as a module. If so, the module | |
11 | will be called nvmem_core. | |
12 | ||
13 | If unsure, say no. | |
4ab11996 SK |
14 | |
15 | if NVMEM | |
16 | ||
17 | config QCOM_QFPROM | |
18 | tristate "QCOM QFPROM Support" | |
19 | depends on ARCH_QCOM || COMPILE_TEST | |
20 | select REGMAP_MMIO | |
21 | help | |
22 | Say y here to enable QFPROM support. The QFPROM provides access | |
23 | functions for QFPROM data to rest of the drivers via nvmem interface. | |
24 | ||
25 | This driver can also be built as a module. If so, the module | |
26 | will be called nvmem_qfprom. | |
27 | ||
3d0b16a6 MR |
28 | config NVMEM_SUNXI_SID |
29 | tristate "Allwinner SoCs SID support" | |
30 | depends on ARCH_SUNXI | |
31 | select REGMAP_MMIO | |
32 | help | |
33 | This is a driver for the 'security ID' available on various Allwinner | |
34 | devices. | |
35 | ||
36 | This driver can also be built as a module. If so, the module | |
37 | will be called nvmem_sunxi_sid. | |
38 | ||
22dbdb7c SM |
39 | config NVMEM_VF610_OCOTP |
40 | tristate "VF610 SoC OCOTP support" | |
41 | depends on SOC_VF610 || COMPILE_TEST | |
42 | help | |
43 | This is a driver for the 'OCOTP' peripheral available on Vybrid | |
44 | devices like VF5xx and VF6xx. | |
45 | ||
46 | This driver can also be build as a module. If so, the module will | |
47 | be called nvmem-vf610-ocotp. | |
48 | ||
4ab11996 | 49 | endif |