Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menu "Multifunction device drivers"
  5. config MISC
  6. bool "Enable Driver Model for Misc drivers"
  7. depends on DM
  8. help
  9. Enable driver model for miscellaneous devices. This class is
  10. used only for those do not fit other more general classes. A
  11. set of generic read, write and ioctl methods may be used to
  12. access the device.
  13. config SPL_MISC
  14. bool "Enable Driver Model for Misc drivers in SPL"
  15. depends on SPL_DM
  16. help
  17. Enable driver model for miscellaneous devices. This class is
  18. used only for those do not fit other more general classes. A
  19. set of generic read, write and ioctl methods may be used to
  20. access the device.
  21. config TPL_MISC
  22. bool "Enable Driver Model for Misc drivers in TPL"
  23. depends on TPL_DM
  24. help
  25. Enable driver model for miscellaneous devices. This class is
  26. used only for those do not fit other more general classes. A
  27. set of generic read, write and ioctl methods may be used to
  28. access the device.
  29. config ALTERA_SYSID
  30. bool "Altera Sysid support"
  31. depends on MISC
  32. help
  33. Select this to enable a sysid for Altera devices. Please find
  34. details on the "Embedded Peripherals IP User Guide" of Altera.
  35. config ATSHA204A
  36. bool "Support for Atmel ATSHA204A module"
  37. depends on MISC
  38. help
  39. Enable support for I2C connected Atmel's ATSHA204A
  40. CryptoAuthentication module found for example on the Turris Omnia
  41. board.
  42. config ROCKCHIP_EFUSE
  43. bool "Rockchip e-fuse support"
  44. depends on MISC
  45. help
  46. Enable (read-only) access for the e-fuse block found in Rockchip
  47. SoCs: accesses can either be made using byte addressing and a length
  48. or through child-nodes that are generated based on the e-fuse map
  49. retrieved from the DTS.
  50. This driver currently supports the RK3399 only, but can easily be
  51. extended (by porting the read function from the Linux kernel sources)
  52. to support other recent Rockchip devices.
  53. config ROCKCHIP_OTP
  54. bool "Rockchip OTP Support"
  55. depends on MISC
  56. help
  57. Enable (read-only) access for the one-time-programmable memory block
  58. found in Rockchip SoCs: accesses can either be made using byte
  59. addressing and a length or through child-nodes that are generated
  60. based on the e-fuse map retrieved from the DTS.
  61. config SIFIVE_OTP
  62. bool "SiFive eMemory OTP driver"
  63. depends on MISC
  64. help
  65. Enable support for reading and writing the eMemory OTP on the
  66. SiFive SoCs.
  67. config VEXPRESS_CONFIG
  68. bool "Enable support for Arm Versatile Express config bus"
  69. depends on MISC
  70. help
  71. If you say Y here, you will get support for accessing the
  72. configuration bus on the Arm Versatile Express boards via
  73. a sysreg driver.
  74. config CMD_CROS_EC
  75. bool "Enable crosec command"
  76. depends on CROS_EC
  77. help
  78. Enable command-line access to the Chrome OS EC (Embedded
  79. Controller). This provides the 'crosec' command which has
  80. a number of sub-commands for performing EC tasks such as
  81. updating its flash, accessing a small saved context area
  82. and talking to the I2C bus behind the EC (if there is one).
  83. config CROS_EC
  84. bool "Enable Chrome OS EC"
  85. help
  86. Enable access to the Chrome OS EC. This is a separate
  87. microcontroller typically available on a SPI bus on Chromebooks. It
  88. provides access to the keyboard, some internal storage and may
  89. control access to the battery and main PMIC depending on the
  90. device. You can use the 'crosec' command to access it.
  91. config SPL_CROS_EC
  92. bool "Enable Chrome OS EC in SPL"
  93. depends on SPL
  94. help
  95. Enable access to the Chrome OS EC in SPL. This is a separate
  96. microcontroller typically available on a SPI bus on Chromebooks. It
  97. provides access to the keyboard, some internal storage and may
  98. control access to the battery and main PMIC depending on the
  99. device. You can use the 'crosec' command to access it.
  100. config TPL_CROS_EC
  101. bool "Enable Chrome OS EC in TPL"
  102. depends on TPL
  103. help
  104. Enable access to the Chrome OS EC in TPL. This is a separate
  105. microcontroller typically available on a SPI bus on Chromebooks. It
  106. provides access to the keyboard, some internal storage and may
  107. control access to the battery and main PMIC depending on the
  108. device. You can use the 'crosec' command to access it.
  109. config CROS_EC_I2C
  110. bool "Enable Chrome OS EC I2C driver"
  111. depends on CROS_EC
  112. help
  113. Enable I2C access to the Chrome OS EC. This is used on older
  114. ARM Chromebooks such as snow and spring before the standard bus
  115. changed to SPI. The EC will accept commands across the I2C using
  116. a special message protocol, and provide responses.
  117. config CROS_EC_LPC
  118. bool "Enable Chrome OS EC LPC driver"
  119. depends on CROS_EC
  120. help
  121. Enable I2C access to the Chrome OS EC. This is used on x86
  122. Chromebooks such as link and falco. The keyboard is provided
  123. through a legacy port interface, so on x86 machines the main
  124. function of the EC is power and thermal management.
  125. config SPL_CROS_EC_LPC
  126. bool "Enable Chrome OS EC LPC driver in SPL"
  127. depends on CROS_EC
  128. help
  129. Enable I2C access to the Chrome OS EC. This is used on x86
  130. Chromebooks such as link and falco. The keyboard is provided
  131. through a legacy port interface, so on x86 machines the main
  132. function of the EC is power and thermal management.
  133. config TPL_CROS_EC_LPC
  134. bool "Enable Chrome OS EC LPC driver in TPL"
  135. depends on CROS_EC
  136. help
  137. Enable I2C access to the Chrome OS EC. This is used on x86
  138. Chromebooks such as link and falco. The keyboard is provided
  139. through a legacy port interface, so on x86 machines the main
  140. function of the EC is power and thermal management.
  141. config CROS_EC_SANDBOX
  142. bool "Enable Chrome OS EC sandbox driver"
  143. depends on CROS_EC && SANDBOX
  144. help
  145. Enable a sandbox emulation of the Chrome OS EC. This supports
  146. keyboard (use the -l flag to enable the LCD), verified boot context,
  147. EC flash read/write/erase support and a few other things. It is
  148. enough to perform a Chrome OS verified boot on sandbox.
  149. config SPL_CROS_EC_SANDBOX
  150. bool "Enable Chrome OS EC sandbox driver in SPL"
  151. depends on SPL_CROS_EC && SANDBOX
  152. help
  153. Enable a sandbox emulation of the Chrome OS EC in SPL. This supports
  154. keyboard (use the -l flag to enable the LCD), verified boot context,
  155. EC flash read/write/erase support and a few other things. It is
  156. enough to perform a Chrome OS verified boot on sandbox.
  157. config TPL_CROS_EC_SANDBOX
  158. bool "Enable Chrome OS EC sandbox driver in TPL"
  159. depends on TPL_CROS_EC && SANDBOX
  160. help
  161. Enable a sandbox emulation of the Chrome OS EC in TPL. This supports
  162. keyboard (use the -l flag to enable the LCD), verified boot context,
  163. EC flash read/write/erase support and a few other things. It is
  164. enough to perform a Chrome OS verified boot on sandbox.
  165. config CROS_EC_SPI
  166. bool "Enable Chrome OS EC SPI driver"
  167. depends on CROS_EC
  168. help
  169. Enable SPI access to the Chrome OS EC. This is used on newer
  170. ARM Chromebooks such as pit, pi and nyan-big. The SPI interface
  171. provides a faster and more robust interface than I2C but the bugs
  172. are less interesting.
  173. config DS4510
  174. bool "Enable support for DS4510 CPU supervisor"
  175. help
  176. Enable support for the Maxim DS4510 CPU supervisor. It has an
  177. integrated 64-byte EEPROM, four programmable non-volatile I/O pins
  178. and a configurable timer for the supervisor function. The device is
  179. connected over I2C.
  180. config FSL_SEC_MON
  181. bool "Enable FSL SEC_MON Driver"
  182. help
  183. Freescale Security Monitor block is responsible for monitoring
  184. system states.
  185. Security Monitor can be transitioned on any security failures,
  186. like software violations or hardware security violations.
  187. config IRQ
  188. bool "Interrupt controller"
  189. help
  190. This enables support for interrupt controllers, including ITSS.
  191. Some devices have extra features, such as Apollo Lake. The
  192. device has its own uclass since there are several operations
  193. involved.
  194. config JZ4780_EFUSE
  195. bool "Ingenic JZ4780 eFUSE support"
  196. depends on ARCH_JZ47XX
  197. help
  198. This selects support for the eFUSE on Ingenic JZ4780 SoCs.
  199. config MXC_OCOTP
  200. bool "Enable MXC OCOTP Driver"
  201. depends on ARCH_IMX8M || ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_VF610
  202. default y
  203. help
  204. If you say Y here, you will get support for the One Time
  205. Programmable memory pages that are stored on the some
  206. Freescale i.MX processors.
  207. config NUVOTON_NCT6102D
  208. bool "Enable Nuvoton NCT6102D Super I/O driver"
  209. help
  210. If you say Y here, you will get support for the Nuvoton
  211. NCT6102D Super I/O driver. This can be used to enable or
  212. disable the legacy UART, the watchdog or other devices
  213. in the Nuvoton Super IO chips on X86 platforms.
  214. config P2SB
  215. bool "Intel Primary to Sideband Bridge"
  216. depends on X86 || SANDBOX
  217. help
  218. This enables support for the Intel Primary to Sideband Bridge,
  219. abbreviated to P2SB. The P2SB is used to access various peripherals
  220. such as eSPI, GPIO, through memory-mapped I/O in a large chunk of PCI
  221. space. The space is segmented into different channels and peripherals
  222. are accessed by device-specific means within those channels. Devices
  223. should be added in the device tree as subnodes of the P2SB. A
  224. Peripheral Channel Register? (PCR) API is provided to access those
  225. devices - see pcr_readl(), etc.
  226. config SPL_P2SB
  227. bool "Intel Primary to Sideband Bridge in SPL"
  228. depends on SPL && (X86 || SANDBOX)
  229. help
  230. The Primary to Sideband Bridge is used to access various peripherals
  231. through memory-mapped I/O in a large chunk of PCI space. The space is
  232. segmented into different channels and peripherals are accessed by
  233. device-specific means within those channels. Devices should be added
  234. in the device tree as subnodes of the p2sb.
  235. config TPL_P2SB
  236. bool "Intel Primary to Sideband Bridge in TPL"
  237. depends on TPL && (X86 || SANDBOX)
  238. help
  239. The Primary to Sideband Bridge is used to access various peripherals
  240. through memory-mapped I/O in a large chunk of PCI space. The space is
  241. segmented into different channels and peripherals are accessed by
  242. device-specific means within those channels. Devices should be added
  243. in the device tree as subnodes of the p2sb.
  244. config PWRSEQ
  245. bool "Enable power-sequencing drivers"
  246. depends on DM
  247. help
  248. Power-sequencing drivers provide support for controlling power for
  249. devices. They are typically referenced by a phandle from another
  250. device. When the device is started up, its power sequence can be
  251. initiated.
  252. config SPL_PWRSEQ
  253. bool "Enable power-sequencing drivers for SPL"
  254. depends on PWRSEQ
  255. help
  256. Power-sequencing drivers provide support for controlling power for
  257. devices. They are typically referenced by a phandle from another
  258. device. When the device is started up, its power sequence can be
  259. initiated.
  260. config PCA9551_LED
  261. bool "Enable PCA9551 LED driver"
  262. help
  263. Enable driver for PCA9551 LED controller. This controller
  264. is connected via I2C. So I2C needs to be enabled.
  265. config PCA9551_I2C_ADDR
  266. hex "I2C address of PCA9551 LED controller"
  267. depends on PCA9551_LED
  268. default 0x60
  269. help
  270. The I2C address of the PCA9551 LED controller.
  271. config STM32MP_FUSE
  272. bool "Enable STM32MP fuse wrapper providing the fuse API"
  273. depends on ARCH_STM32MP && MISC
  274. default y if CMD_FUSE
  275. help
  276. If you say Y here, you will get support for the fuse API (OTP)
  277. for STM32MP architecture.
  278. This API is needed for CMD_FUSE.
  279. config STM32_RCC
  280. bool "Enable RCC driver for the STM32 SoC's family"
  281. depends on (ARCH_STM32 || ARCH_STM32MP) && MISC
  282. help
  283. Enable the STM32 RCC driver. The RCC block (Reset and Clock Control
  284. block) is responsible of the management of the clock and reset
  285. generation.
  286. This driver is similar to an MFD driver in the Linux kernel.
  287. config TEGRA_CAR
  288. bool "Enable support for the Tegra CAR driver"
  289. depends on TEGRA_NO_BPMP
  290. help
  291. The Tegra CAR (Clock and Reset Controller) is a HW module that
  292. controls almost all clocks and resets in a Tegra SoC.
  293. config TEGRA186_BPMP
  294. bool "Enable support for the Tegra186 BPMP driver"
  295. depends on TEGRA186
  296. help
  297. The Tegra BPMP (Boot and Power Management Processor) is a separate
  298. auxiliary CPU embedded into Tegra to perform power management work,
  299. and controls related features such as clocks, resets, power domains,
  300. PMIC I2C bus, etc. This driver provides the core low-level
  301. communication path by which feature-specific drivers (such as clock)
  302. can make requests to the BPMP. This driver is similar to an MFD
  303. driver in the Linux kernel.
  304. config TEST_DRV
  305. bool "Enable support for test drivers"
  306. default y if SANDBOX
  307. help
  308. This enables drivers and uclasses that provides a way of testing the
  309. operations of memory allocation and driver/uclass methods in driver
  310. model. This should only be enabled for testing as it is not useful for
  311. anything else.
  312. config TWL4030_LED
  313. bool "Enable TWL4030 LED controller"
  314. help
  315. Enable this to add support for the TWL4030 LED controller.
  316. config WINBOND_W83627
  317. bool "Enable Winbond Super I/O driver"
  318. help
  319. If you say Y here, you will get support for the Winbond
  320. W83627 Super I/O driver. This can be used to enable the
  321. legacy UART or other devices in the Winbond Super IO chips
  322. on X86 platforms.
  323. config QFW
  324. bool
  325. help
  326. Hidden option to enable QEMU fw_cfg interface and uclass. This will
  327. be selected by either CONFIG_CMD_QFW or CONFIG_GENERATE_ACPI_TABLE.
  328. config QFW_PIO
  329. bool
  330. depends on QFW
  331. help
  332. Hidden option to enable PIO QEMU fw_cfg interface. This will be
  333. selected by the appropriate QEMU board.
  334. config QFW_MMIO
  335. bool
  336. depends on QFW
  337. help
  338. Hidden option to enable MMIO QEMU fw_cfg interface. This will be
  339. selected by the appropriate QEMU board.
  340. config I2C_EEPROM
  341. bool "Enable driver for generic I2C-attached EEPROMs"
  342. depends on MISC
  343. help
  344. Enable a generic driver for EEPROMs attached via I2C.
  345. config SPL_I2C_EEPROM
  346. bool "Enable driver for generic I2C-attached EEPROMs for SPL"
  347. depends on MISC && SPL && SPL_DM
  348. help
  349. This option is an SPL-variant of the I2C_EEPROM option.
  350. See the help of I2C_EEPROM for details.
  351. if I2C_EEPROM
  352. config SYS_I2C_EEPROM_ADDR
  353. hex "Chip address of the EEPROM device"
  354. default 0
  355. config SYS_I2C_EEPROM_BUS
  356. int "I2C bus of the EEPROM device."
  357. default 0
  358. config SYS_EEPROM_SIZE
  359. int "Size in bytes of the EEPROM device"
  360. default 256
  361. config SYS_EEPROM_PAGE_WRITE_BITS
  362. int "Number of bits used to address bytes in a single page"
  363. default 0
  364. help
  365. The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
  366. A 64 byte page, for example would require six bits.
  367. config SYS_EEPROM_PAGE_WRITE_DELAY_MS
  368. int "Number of milliseconds to delay between page writes"
  369. default 0
  370. config SYS_I2C_EEPROM_ADDR_LEN
  371. int "Length in bytes of the EEPROM memory array address"
  372. default 1
  373. help
  374. Note: This is NOT the chip address length!
  375. config SYS_I2C_EEPROM_ADDR_OVERFLOW
  376. hex "EEPROM Address Overflow"
  377. default 0
  378. help
  379. EEPROM chips that implement "address overflow" are ones
  380. like Catalyst 24WC04/08/16 which has 9/10/11 bits of
  381. address and the extra bits end up in the "chip address" bit
  382. slots. This makes a 24WC08 (1Kbyte) chip look like four 256
  383. byte chips.
  384. endif
  385. config GDSYS_RXAUI_CTRL
  386. bool "Enable gdsys RXAUI control driver"
  387. depends on MISC
  388. help
  389. Support gdsys FPGA's RXAUI control.
  390. config GDSYS_IOEP
  391. bool "Enable gdsys IOEP driver"
  392. depends on MISC
  393. help
  394. Support gdsys FPGA's IO endpoint driver.
  395. config MPC83XX_SERDES
  396. bool "Enable MPC83xx serdes driver"
  397. depends on MISC
  398. help
  399. Support for serdes found on MPC83xx SoCs.
  400. config FS_LOADER
  401. bool "Enable loader driver for file system"
  402. help
  403. This is file system generic loader which can be used to load
  404. the file image from the storage into target such as memory.
  405. The consumer driver would then use this loader to program whatever,
  406. ie. the FPGA device.
  407. config GDSYS_SOC
  408. bool "Enable gdsys SOC driver"
  409. depends on MISC
  410. help
  411. Support for gdsys IHS SOC, a simple bus associated with each gdsys
  412. IHS (Integrated Hardware Systems) FPGA, which holds all devices whose
  413. register maps are contained within the FPGA's register map.
  414. config IHS_FPGA
  415. bool "Enable IHS FPGA driver"
  416. depends on MISC
  417. help
  418. Support IHS (Integrated Hardware Systems) FPGA, the main FPGAs on
  419. gdsys devices, which supply the majority of the functionality offered
  420. by the devices. This driver supports both CON and CPU variants of the
  421. devices, depending on the device tree entry.
  422. config ESM_K3
  423. bool "Enable K3 ESM driver"
  424. depends on ARCH_K3
  425. help
  426. Support ESM (Error Signaling Module) on TI K3 SoCs.
  427. config MICROCHIP_FLEXCOM
  428. bool "Enable Microchip Flexcom driver"
  429. depends on MISC
  430. help
  431. The Atmel Flexcom is just a wrapper which embeds a SPI controller,
  432. an I2C controller and an USART.
  433. Only one function can be used at a time and is chosen at boot time
  434. according to the device tree.
  435. config K3_AVS0
  436. depends on ARCH_K3 && SPL_DM_REGULATOR
  437. bool "AVS class 0 support for K3 devices"
  438. help
  439. K3 devices have the optimized voltage values for the main voltage
  440. domains stored in efuse within the VTM IP. This driver reads the
  441. optimized voltage from the efuse, so that it can be programmed
  442. to the PMIC on board.
  443. config ESM_PMIC
  444. bool "Enable PMIC ESM driver"
  445. depends on DM_PMIC
  446. help
  447. Support ESM (Error Signal Monitor) on PMIC devices. ESM is used
  448. typically to reboot the board in error condition.
  449. endmenu