Kconfig 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. menu "EEPROM support"
  3. config EEPROM_AT24
  4. tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
  5. depends on I2C && SYSFS
  6. select NVMEM
  7. select NVMEM_SYSFS
  8. select REGMAP
  9. select REGMAP_I2C
  10. help
  11. Enable this driver to get read/write support to most I2C EEPROMs
  12. and compatible devices like FRAMs, SRAMs, ROMs etc. After you
  13. configure the driver to know about each chip on your target
  14. board. Use these generic chip names, instead of vendor-specific
  15. ones like at24c64, 24lc02 or fm24c04:
  16. 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
  17. 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024, 24c2048
  18. Unless you like data loss puzzles, always be sure that any chip
  19. you configure as a 24c32 (32 kbit) or larger is NOT really a
  20. 24c16 (16 kbit) or smaller, and vice versa. Marking the chip
  21. as read-only won't help recover from this. Also, if your chip
  22. has any software write-protect mechanism you may want to review the
  23. code to make sure this driver won't turn it on by accident.
  24. If you use this with an SMBus adapter instead of an I2C adapter,
  25. full functionality is not available. Only smaller devices are
  26. supported (24c16 and below, max 4 kByte).
  27. This driver can also be built as a module. If so, the module
  28. will be called at24.
  29. config EEPROM_AT25
  30. tristate "SPI EEPROMs (FRAMs) from most vendors"
  31. depends on SPI && SYSFS
  32. select NVMEM
  33. select NVMEM_SYSFS
  34. select SPI_MEM
  35. help
  36. Enable this driver to get read/write support to most SPI EEPROMs
  37. and Cypress FRAMs,
  38. after you configure the board init code to know about each eeprom
  39. on your target board.
  40. This driver can also be built as a module. If so, the module
  41. will be called at25.
  42. config EEPROM_MAX6875
  43. tristate "Maxim MAX6874/5 power supply supervisor"
  44. depends on I2C
  45. help
  46. If you say yes here you get read-only support for the user EEPROM of
  47. the Maxim MAX6874/5 EEPROM-programmable, quad power-supply
  48. sequencer/supervisor.
  49. All other features of this chip should be accessed via i2c-dev.
  50. This driver can also be built as a module. If so, the module
  51. will be called max6875.
  52. config EEPROM_93CX6
  53. tristate "EEPROM 93CX6 support"
  54. help
  55. This is a driver for the EEPROM chipsets 93c46 and 93c66.
  56. The driver supports both read as well as write commands.
  57. If unsure, say N.
  58. config EEPROM_93XX46
  59. tristate "Microwire EEPROM 93XX46 support"
  60. depends on SPI && SYSFS
  61. select REGMAP
  62. select NVMEM
  63. select NVMEM_SYSFS
  64. help
  65. Driver for the microwire EEPROM chipsets 93xx46x. The driver
  66. supports both read and write commands and also the command to
  67. erase the whole EEPROM.
  68. This driver can also be built as a module. If so, the module
  69. will be called eeprom_93xx46.
  70. If unsure, say N.
  71. config EEPROM_DIGSY_MTC_CFG
  72. bool "DigsyMTC display configuration EEPROMs device"
  73. depends on GPIO_MPC5200 && SPI_GPIO
  74. help
  75. This option enables access to display configuration EEPROMs
  76. on digsy_mtc board. You have to additionally select Microwire
  77. EEPROM 93XX46 driver. sysfs entries will be created for that
  78. EEPROM allowing to read/write the configuration data or to
  79. erase the whole EEPROM.
  80. If unsure, say N.
  81. config EEPROM_IDT_89HPESX
  82. tristate "IDT 89HPESx PCIe-switches EEPROM / CSR support"
  83. depends on I2C && SYSFS
  84. help
  85. Enable this driver to get read/write access to EEPROM / CSRs
  86. over IDT PCIe-switch i2c-slave interface.
  87. This driver can also be built as a module. If so, the module
  88. will be called idt_89hpesx.
  89. config EEPROM_EE1004
  90. tristate "SPD EEPROMs on DDR4 memory modules"
  91. depends on I2C && SYSFS
  92. select NVMEM
  93. select NVMEM_SYSFS
  94. help
  95. Enable this driver to get read support to SPD EEPROMs following
  96. the JEDEC EE1004 standard. These are typically found on DDR4
  97. SDRAM memory modules.
  98. This driver can also be built as a module. If so, the module
  99. will be called ee1004.
  100. config EEPROM_M24LR
  101. tristate "STMicroelectronics M24LR RFID/NFC EEPROM support"
  102. depends on I2C && SYSFS
  103. select REGMAP_I2C
  104. select NVMEM
  105. select NVMEM_SYSFS
  106. help
  107. This enables support for STMicroelectronics M24LR RFID/NFC EEPROM
  108. chips. These dual-interface devices expose two I2C addresses:
  109. one for EEPROM memory access and another for control and system
  110. configuration (e.g. UID, password handling).
  111. This driver provides a sysfs interface for control functions and
  112. integrates with the nvmem subsystem for EEPROM access.
  113. To compile this driver as a module, choose M here: the
  114. module will be called m24lr.
  115. endmenu