2 # Multifunction miscellaneous devices
5 menu "Multifunction device drivers"
8 bool "Enable Driver Model for Misc drivers"
11 Enable driver model for miscellaneous devices. This class is
12 used only for those do not fit other more general classes. A
13 set of generic read, write and ioctl methods may be used to
17 bool "Enable Driver Model for Misc drivers in SPL"
21 Enable driver model for miscellaneous devices. This class is
22 used only for those do not fit other more general classes. A
23 set of generic read, write and ioctl methods may be used to
27 bool "Enable Driver Model for Misc drivers in TPL"
31 Enable driver model for miscellaneous devices. This class is
32 used only for those do not fit other more general classes. A
33 set of generic read, write and ioctl methods may be used to
37 bool "Enable Driver Model for Misc drivers in VPL"
41 Enable driver model for miscellaneous devices. This class is
42 used only for those do not fit other more general classes. A
43 set of generic read, write and ioctl methods may be used to
49 This adds support for a common interface to different types of
50 non-volatile memory. Consumers can use nvmem-cells properties to look
51 up hardware configuration data such as MAC addresses and calibration
55 bool "NVMEM support in SPL"
57 This adds support for a common interface to different types of
58 non-volatile memory. Consumers can use nvmem-cells properties to look
59 up hardware configuration data such as MAC addresses and calibration
63 bool "Altera Sysid support"
66 Select this to enable a sysid for Altera devices. Please find
67 details on the "Embedded Peripherals IP User Guide" of Altera.
70 bool "Support for Atmel ATSHA204A module"
74 Enable support for I2C connected Atmel's ATSHA204A
75 CryptoAuthentication module found for example on the Turris Omnia
79 bool "Gateworks System Controller Support"
82 Enable access for the Gateworks System Controller used on Gateworks
83 boards to provide a boot watchdog, power control, temperature monitor,
84 voltage ADCs, and EEPROM.
87 bool "Rockchip e-fuse support"
90 Enable (read-only) access for the e-fuse block found in Rockchip
91 SoCs: accesses can either be made using byte addressing and a length
92 or through child-nodes that are generated based on the e-fuse map
93 retrieved from the DTS.
95 This driver currently supports the RK3399 only, but can easily be
96 extended (by porting the read function from the Linux kernel sources)
97 to support other recent Rockchip devices.
100 bool "Rockchip OTP Support"
103 Enable (read-only) access for the one-time-programmable memory block
104 found in Rockchip SoCs: accesses can either be made using byte
105 addressing and a length or through child-nodes that are generated
106 based on the e-fuse map retrieved from the DTS.
109 bool "SiFive eMemory OTP driver"
112 Enable support for reading and writing the eMemory OTP on the
115 config VEXPRESS_CONFIG
116 bool "Enable support for Arm Versatile Express config bus"
119 If you say Y here, you will get support for accessing the
120 configuration bus on the Arm Versatile Express boards via
124 bool "Enable crosec command"
127 Enable command-line access to the Chrome OS EC (Embedded
128 Controller). This provides the 'crosec' command which has
129 a number of sub-commands for performing EC tasks such as
130 updating its flash, accessing a small saved context area
131 and talking to the I2C bus behind the EC (if there is one).
134 bool "Enable Chrome OS EC"
136 Enable access to the Chrome OS EC. This is a separate
137 microcontroller typically available on a SPI bus on Chromebooks. It
138 provides access to the keyboard, some internal storage and may
139 control access to the battery and main PMIC depending on the
140 device. You can use the 'crosec' command to access it.
143 bool "Enable Chrome OS EC in SPL"
146 Enable access to the Chrome OS EC in SPL. This is a separate
147 microcontroller typically available on a SPI bus on Chromebooks. It
148 provides access to the keyboard, some internal storage and may
149 control access to the battery and main PMIC depending on the
150 device. You can use the 'crosec' command to access it.
153 bool "Enable Chrome OS EC in TPL"
156 Enable access to the Chrome OS EC in TPL. This is a separate
157 microcontroller typically available on a SPI bus on Chromebooks. It
158 provides access to the keyboard, some internal storage and may
159 control access to the battery and main PMIC depending on the
160 device. You can use the 'crosec' command to access it.
163 bool "Enable Chrome OS EC in VPL"
166 Enable access to the Chrome OS EC in VPL. This is a separate
167 microcontroller typically available on a SPI bus on Chromebooks. It
168 provides access to the keyboard, some internal storage and may
169 control access to the battery and main PMIC depending on the
170 device. You can use the 'crosec' command to access it.
173 bool "Enable Chrome OS EC I2C driver"
176 Enable I2C access to the Chrome OS EC. This is used on older
177 ARM Chromebooks such as snow and spring before the standard bus
178 changed to SPI. The EC will accept commands across the I2C using
179 a special message protocol, and provide responses.
182 bool "Enable Chrome OS EC LPC driver"
185 Enable I2C access to the Chrome OS EC. This is used on x86
186 Chromebooks such as link and falco. The keyboard is provided
187 through a legacy port interface, so on x86 machines the main
188 function of the EC is power and thermal management.
190 config SPL_CROS_EC_LPC
191 bool "Enable Chrome OS EC LPC driver in SPL"
192 depends on CROS_EC && SPL_MISC
194 Enable I2C access to the Chrome OS EC. This is used on x86
195 Chromebooks such as link and falco. The keyboard is provided
196 through a legacy port interface, so on x86 machines the main
197 function of the EC is power and thermal management.
199 config TPL_CROS_EC_LPC
200 bool "Enable Chrome OS EC LPC driver in TPL"
201 depends on CROS_EC && TPL_MISC
203 Enable I2C access to the Chrome OS EC. This is used on x86
204 Chromebooks such as link and falco. The keyboard is provided
205 through a legacy port interface, so on x86 machines the main
206 function of the EC is power and thermal management.
208 config VPL_CROS_EC_LPC
209 bool "Enable Chrome OS EC LPC driver in VPL"
210 depends on CROS_EC && VPL_MISC
212 Enable I2C access to the Chrome OS EC. This is used on x86
213 Chromebooks such as link and falco. The keyboard is provided
214 through a legacy port interface, so on x86 machines the main
215 function of the EC is power and thermal management.
217 config CROS_EC_SANDBOX
218 bool "Enable Chrome OS EC sandbox driver"
219 depends on CROS_EC && SANDBOX
221 Enable a sandbox emulation of the Chrome OS EC. This supports
222 keyboard (use the -l flag to enable the LCD), verified boot context,
223 EC flash read/write/erase support and a few other things. It is
224 enough to perform a Chrome OS verified boot on sandbox.
226 config SPL_CROS_EC_SANDBOX
227 bool "Enable Chrome OS EC sandbox driver in SPL"
228 depends on SPL_CROS_EC && SANDBOX
230 Enable a sandbox emulation of the Chrome OS EC in SPL. This supports
231 keyboard (use the -l flag to enable the LCD), verified boot context,
232 EC flash read/write/erase support and a few other things. It is
233 enough to perform a Chrome OS verified boot on sandbox.
235 config TPL_CROS_EC_SANDBOX
236 bool "Enable Chrome OS EC sandbox driver in TPL"
237 depends on TPL_CROS_EC && SANDBOX
239 Enable a sandbox emulation of the Chrome OS EC in TPL. This supports
240 keyboard (use the -l flag to enable the LCD), verified boot context,
241 EC flash read/write/erase support and a few other things. It is
242 enough to perform a Chrome OS verified boot on sandbox.
244 config VPL_CROS_EC_SANDBOX
245 bool "Enable Chrome OS EC sandbox driver in VPL"
246 depends on VPL_CROS_EC && SANDBOX
248 Enable a sandbox emulation of the Chrome OS EC in VPL. This supports
249 keyboard (use the -l flag to enable the LCD), verified boot context,
250 EC flash read/write/erase support and a few other things. It is
251 enough to perform a Chrome OS verified boot on sandbox.
254 bool "Enable Chrome OS EC SPI driver"
257 Enable SPI access to the Chrome OS EC. This is used on newer
258 ARM Chromebooks such as pit, pi and nyan-big. The SPI interface
259 provides a faster and more robust interface than I2C but the bugs
260 are less interesting.
263 bool "Enable support for DS4510 CPU supervisor"
265 Enable support for the Maxim DS4510 CPU supervisor. It has an
266 integrated 64-byte EEPROM, four programmable non-volatile I/O pins
267 and a configurable timer for the supervisor function. The device is
271 bool "Enable FSL SEC_MON Driver"
273 Freescale Security Monitor block is responsible for monitoring
275 Security Monitor can be transitioned on any security failures,
276 like software violations or hardware security violations.
279 bool "Interrupt controller"
281 This enables support for interrupt controllers, including ITSS.
282 Some devices have extra features, such as Apollo Lake. The
283 device has its own uclass since there are several operations
287 bool "Ingenic JZ4780 eFUSE support"
288 depends on ARCH_JZ47XX
290 This selects support for the eFUSE on Ingenic JZ4780 SoCs.
293 bool "Enable MXC OCOTP Driver"
294 depends on ARCH_IMX8M || ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_VF610
297 If you say Y here, you will get support for the One Time
298 Programmable memory pages that are stored on the some
299 Freescale i.MX processors.
302 bool "Enable MXC OCOTP driver in SPL"
303 depends on SPL_MISC && (ARCH_IMX8M || ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_VF610)
306 If you say Y here, you will get support for the One Time
307 Programmable memory pages, that are stored on some
308 Freescale i.MX processors, in SPL.
310 config NUVOTON_NCT6102D
311 bool "Enable Nuvoton NCT6102D Super I/O driver"
313 If you say Y here, you will get support for the Nuvoton
314 NCT6102D Super I/O driver. This can be used to enable or
315 disable the legacy UART, the watchdog or other devices
316 in the Nuvoton Super IO chips on X86 platforms.
319 bool "Intel Primary to Sideband Bridge"
320 depends on X86 || SANDBOX
322 This enables support for the Intel Primary to Sideband Bridge,
323 abbreviated to P2SB. The P2SB is used to access various peripherals
324 such as eSPI, GPIO, through memory-mapped I/O in a large chunk of PCI
325 space. The space is segmented into different channels and peripherals
326 are accessed by device-specific means within those channels. Devices
327 should be added in the device tree as subnodes of the P2SB. A
328 Peripheral Channel Register? (PCR) API is provided to access those
329 devices - see pcr_readl(), etc.
332 bool "Intel Primary to Sideband Bridge in SPL"
333 depends on SPL_MISC && (X86 || SANDBOX)
335 The Primary to Sideband Bridge is used to access various peripherals
336 through memory-mapped I/O in a large chunk of PCI space. The space is
337 segmented into different channels and peripherals are accessed by
338 device-specific means within those channels. Devices should be added
339 in the device tree as subnodes of the p2sb.
342 bool "Intel Primary to Sideband Bridge in TPL"
343 depends on TPL_MISC && (X86 || SANDBOX)
345 The Primary to Sideband Bridge is used to access various peripherals
346 through memory-mapped I/O in a large chunk of PCI space. The space is
347 segmented into different channels and peripherals are accessed by
348 device-specific means within those channels. Devices should be added
349 in the device tree as subnodes of the p2sb.
352 bool "Enable power-sequencing drivers"
355 Power-sequencing drivers provide support for controlling power for
356 devices. They are typically referenced by a phandle from another
357 device. When the device is started up, its power sequence can be
361 bool "Enable power-sequencing drivers for SPL"
362 depends on SPL_MISC && PWRSEQ
364 Power-sequencing drivers provide support for controlling power for
365 devices. They are typically referenced by a phandle from another
366 device. When the device is started up, its power sequence can be
370 bool "Enable PCA9551 LED driver"
372 Enable driver for PCA9551 LED controller. This controller
373 is connected via I2C. So I2C needs to be enabled.
375 config PCA9551_I2C_ADDR
376 hex "I2C address of PCA9551 LED controller"
377 depends on PCA9551_LED
380 The I2C address of the PCA9551 LED controller.
383 bool "Enable STM32MP fuse wrapper providing the fuse API"
384 depends on ARCH_STM32MP && MISC
385 default y if CMD_FUSE
387 If you say Y here, you will get support for the fuse API (OTP)
388 for STM32MP architecture.
389 This API is needed for CMD_FUSE.
392 bool "Enable RCC driver for the STM32 SoC's family"
393 depends on (ARCH_STM32 || ARCH_STM32MP) && MISC
395 Enable the STM32 RCC driver. The RCC block (Reset and Clock Control
396 block) is responsible of the management of the clock and reset
398 This driver is similar to an MFD driver in the Linux kernel.
401 bool "Enable support for the Tegra CAR driver"
402 depends on TEGRA_NO_BPMP
404 The Tegra CAR (Clock and Reset Controller) is a HW module that
405 controls almost all clocks and resets in a Tegra SoC.
408 bool "Enable support for the Tegra186 BPMP driver"
411 The Tegra BPMP (Boot and Power Management Processor) is a separate
412 auxiliary CPU embedded into Tegra to perform power management work,
413 and controls related features such as clocks, resets, power domains,
414 PMIC I2C bus, etc. This driver provides the core low-level
415 communication path by which feature-specific drivers (such as clock)
416 can make requests to the BPMP. This driver is similar to an MFD
417 driver in the Linux kernel.
420 bool "Enable support for test drivers"
423 This enables drivers and uclasses that provides a way of testing the
424 operations of memory allocation and driver/uclass methods in driver
425 model. This should only be enabled for testing as it is not useful for
429 bool "Enable TWL4030 LED controller"
431 Enable this to add support for the TWL4030 LED controller.
433 config WINBOND_W83627
434 bool "Enable Winbond Super I/O driver"
436 If you say Y here, you will get support for the Winbond
437 W83627 Super I/O driver. This can be used to enable the
438 legacy UART or other devices in the Winbond Super IO chips
444 Hidden option to enable QEMU fw_cfg interface and uclass. This will
445 be selected by either CONFIG_CMD_QFW or CONFIG_GENERATE_ACPI_TABLE.
451 Hidden option to enable PIO QEMU fw_cfg interface. This will be
452 selected by the appropriate QEMU board.
458 Hidden option to enable MMIO QEMU fw_cfg interface. This will be
459 selected by the appropriate QEMU board.
462 bool "Enable driver for generic I2C-attached EEPROMs"
465 Enable a generic driver for EEPROMs attached via I2C.
468 config SPL_I2C_EEPROM
469 bool "Enable driver for generic I2C-attached EEPROMs for SPL"
472 This option is an SPL-variant of the I2C_EEPROM option.
473 See the help of I2C_EEPROM for details.
475 config SYS_I2C_EEPROM_ADDR
476 hex "Chip address of the EEPROM device"
477 depends on ID_EEPROM || I2C_EEPROM || SPL_I2C_EEPROM || CMD_EEPROM || ENV_IS_IN_EEPROM
482 config SYS_I2C_EEPROM_ADDR_OVERFLOW
483 hex "EEPROM Address Overflow"
486 EEPROM chips that implement "address overflow" are ones
487 like Catalyst 24WC04/08/16 which has 9/10/11 bits of
488 address and the extra bits end up in the "chip address" bit
489 slots. This makes a 24WC08 (1Kbyte) chip look like four 256
494 config GDSYS_RXAUI_CTRL
495 bool "Enable gdsys RXAUI control driver"
498 Support gdsys FPGA's RXAUI control.
501 bool "Enable gdsys IOEP driver"
504 Support gdsys FPGA's IO endpoint driver.
506 config MPC83XX_SERDES
507 bool "Enable MPC83xx serdes driver"
510 Support for serdes found on MPC83xx SoCs.
513 bool "Enable loader driver for file system"
515 This is file system generic loader which can be used to load
516 the file image from the storage into target such as memory.
518 The consumer driver would then use this loader to program whatever,
522 bool "Enable loader driver for file system"
525 This is file system generic loader which can be used to load
526 the file image from the storage into target such as memory.
528 The consumer driver would then use this loader to program whatever,
532 bool "Enable gdsys SOC driver"
535 Support for gdsys IHS SOC, a simple bus associated with each gdsys
536 IHS (Integrated Hardware Systems) FPGA, which holds all devices whose
537 register maps are contained within the FPGA's register map.
540 bool "Enable IHS FPGA driver"
543 Support IHS (Integrated Hardware Systems) FPGA, the main FPGAs on
544 gdsys devices, which supply the majority of the functionality offered
545 by the devices. This driver supports both CON and CPU variants of the
546 devices, depending on the device tree entry.
548 bool "Enable K3 ESM driver"
551 Support ESM (Error Signaling Module) on TI K3 SoCs.
553 config MICROCHIP_FLEXCOM
554 bool "Enable Microchip Flexcom driver"
557 The Atmel Flexcom is just a wrapper which embeds a SPI controller,
558 an I2C controller and an USART.
559 Only one function can be used at a time and is chosen at boot time
560 according to the device tree.
563 depends on ARCH_K3 && SPL_DM_REGULATOR
564 bool "AVS class 0 support for K3 devices"
566 K3 devices have the optimized voltage values for the main voltage
567 domains stored in efuse within the VTM IP. This driver reads the
568 optimized voltage from the efuse, so that it can be programmed
569 to the PMIC on board.
572 bool "Enable PMIC ESM driver"
575 Support ESM (Error Signal Monitor) on PMIC devices. ESM is used
576 typically to reboot the board in error condition.
582 bool "Enable Kontron sl28cpld multi-function driver"
585 Support for the Kontron sl28cpld management controller. This is
586 the base driver which provides common access methods for the