Kconfig 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147
  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 ALTERA_SYSID
  14. bool "Altera Sysid support"
  15. depends on MISC
  16. help
  17. Select this to enable a sysid for Altera devices. Please find
  18. details on the "Embedded Peripherals IP User Guide" of Altera.
  19. config CMD_CROS_EC
  20. bool "Enable crosec command"
  21. depends on CROS_EC
  22. help
  23. Enable command-line access to the Chrome OS EC (Embedded
  24. Controller). This provides the 'crosec' command which has
  25. a number of sub-commands for performing EC tasks such as
  26. updating its flash, accessing a small saved context area
  27. and talking to the I2C bus behind the EC (if there is one).
  28. config CROS_EC
  29. bool "Enable Chrome OS EC"
  30. help
  31. Enable access to the Chrome OS EC. This is a separate
  32. microcontroller typically available on a SPI bus on Chromebooks. It
  33. provides access to the keyboard, some internal storage and may
  34. control access to the battery and main PMIC depending on the
  35. device. You can use the 'crosec' command to access it.
  36. config CROS_EC_I2C
  37. bool "Enable Chrome OS EC I2C driver"
  38. depends on CROS_EC
  39. help
  40. Enable I2C access to the Chrome OS EC. This is used on older
  41. ARM Chromebooks such as snow and spring before the standard bus
  42. changed to SPI. The EC will accept commands across the I2C using
  43. a special message protocol, and provide responses.
  44. config CROS_EC_LPC
  45. bool "Enable Chrome OS EC LPC driver"
  46. depends on CROS_EC
  47. help
  48. Enable I2C access to the Chrome OS EC. This is used on x86
  49. Chromebooks such as link and falco. The keyboard is provided
  50. through a legacy port interface, so on x86 machines the main
  51. function of the EC is power and thermal management.
  52. config CROS_EC_SANDBOX
  53. bool "Enable Chrome OS EC sandbox driver"
  54. depends on CROS_EC && SANDBOX
  55. help
  56. Enable a sandbox emulation of the Chrome OS EC. This supports
  57. keyboard (use the -l flag to enable the LCD), verified boot context,
  58. EC flash read/write/erase support and a few other things. It is
  59. enough to perform a Chrome OS verified boot on sandbox.
  60. config CROS_EC_SPI
  61. bool "Enable Chrome OS EC SPI driver"
  62. depends on CROS_EC
  63. help
  64. Enable SPI access to the Chrome OS EC. This is used on newer
  65. ARM Chromebooks such as pit, pi and nyan-big. The SPI interface
  66. provides a faster and more robust interface than I2C but the bugs
  67. are less interesting.
  68. config FSL_SEC_MON
  69. bool "Enable FSL SEC_MON Driver"
  70. help
  71. Freescale Security Monitor block is responsible for monitoring
  72. system states.
  73. Security Monitor can be transitioned on any security failures,
  74. like software violations or hardware security violations.
  75. config MXC_OCOTP
  76. bool "Enable MXC OCOTP Driver"
  77. help
  78. If you say Y here, you will get support for the One Time
  79. Programmable memory pages that are stored on the some
  80. Freescale i.MX processors.
  81. config PWRSEQ
  82. bool "Enable power-sequencing drivers"
  83. depends on DM
  84. help
  85. Power-sequencing drivers provide support for controlling power for
  86. devices. They are typically referenced by a phandle from another
  87. device. When the device is started up, its power sequence can be
  88. initiated.
  89. config SPL_PWRSEQ
  90. bool "Enable power-sequencing drivers for SPL"
  91. depends on PWRSEQ
  92. help
  93. Power-sequencing drivers provide support for controlling power for
  94. devices. They are typically referenced by a phandle from another
  95. device. When the device is started up, its power sequence can be
  96. initiated.
  97. config PCA9551_LED
  98. bool "Enable PCA9551 LED driver"
  99. help
  100. Enable driver for PCA9551 LED controller. This controller
  101. is connected via I2C. So I2C needs to be enabled.
  102. config PCA9551_I2C_ADDR
  103. hex "I2C address of PCA9551 LED controller"
  104. depends on PCA9551_LED
  105. default 0x60
  106. help
  107. The I2C address of the PCA9551 LED controller.
  108. config RESET
  109. bool "Enable support for reset drivers"
  110. depends on DM
  111. help
  112. Enable reset drivers which can be used to reset the CPU or board.
  113. Each driver can provide a reset method which will be called to
  114. effect a reset. The uclass will try all available drivers when
  115. reset_walk() is called.
  116. config WINBOND_W83627
  117. bool "Enable Winbond Super I/O driver"
  118. help
  119. If you say Y here, you will get support for the Winbond
  120. W83627 Super I/O driver. This can be used to enable the
  121. legacy UART or other devices in the Winbond Super IO chips
  122. on X86 platforms.
  123. config QFW
  124. bool
  125. help
  126. Hidden option to enable QEMU fw_cfg interface. This will be selected by
  127. either CONFIG_CMD_QEMU_FW_CFG or CONFIG_GENERATE_ACPI_TABLE.
  128. endmenu