Kconfig 3.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menu "Multifunction device drivers"
  5. config CMD_CROS_EC
  6. bool "Enable crosec command"
  7. depends on CROS_EC
  8. help
  9. Enable command-line access to the Chrome OS EC (Embedded
  10. Controller). This provides the 'crosec' command which has
  11. a number of sub-commands for performing EC tasks such as
  12. updating its flash, accessing a small saved context area
  13. and talking to the I2C bus behind the EC (if there is one).
  14. config CROS_EC
  15. bool "Enable Chrome OS EC"
  16. help
  17. Enable access to the Chrome OS EC. This is a separate
  18. microcontroller typically available on a SPI bus on Chromebooks. It
  19. provides access to the keyboard, some internal storage and may
  20. control access to the battery and main PMIC depending on the
  21. device. You can use the 'crosec' command to access it.
  22. config CROS_EC_I2C
  23. bool "Enable Chrome OS EC I2C driver"
  24. depends on CROS_EC
  25. help
  26. Enable I2C access to the Chrome OS EC. This is used on older
  27. ARM Chromebooks such as snow and spring before the standard bus
  28. changed to SPI. The EC will accept commands across the I2C using
  29. a special message protocol, and provide responses.
  30. config CROS_EC_LPC
  31. bool "Enable Chrome OS EC LPC driver"
  32. depends on CROS_EC
  33. help
  34. Enable I2C access to the Chrome OS EC. This is used on x86
  35. Chromebooks such as link and falco. The keyboard is provided
  36. through a legacy port interface, so on x86 machines the main
  37. function of the EC is power and thermal management.
  38. config CROS_EC_SANDBOX
  39. bool "Enable Chrome OS EC sandbox driver"
  40. depends on CROS_EC && SANDBOX
  41. help
  42. Enable a sandbox emulation of the Chrome OS EC. This supports
  43. keyboard (use the -l flag to enable the LCD), verified boot context,
  44. EC flash read/write/erase support and a few other things. It is
  45. enough to perform a Chrome OS verified boot on sandbox.
  46. config CROS_EC_SPI
  47. bool "Enable Chrome OS EC SPI driver"
  48. depends on CROS_EC
  49. help
  50. Enable SPI access to the Chrome OS EC. This is used on newer
  51. ARM Chromebooks such as pit, pi and nyan-big. The SPI interface
  52. provides a faster and more robust interface than I2C but the bugs
  53. are less interesting.
  54. config CONFIG_FSL_SEC_MON
  55. bool "Enable FSL SEC_MON Driver"
  56. help
  57. Freescale Security Monitor block is responsible for monitoring
  58. system states.
  59. Security Monitor can be transitioned on any security failures,
  60. like software violations or hardware security violations.
  61. config PCA9551_LED
  62. bool "Enable PCA9551 LED driver"
  63. help
  64. Enable driver for PCA9551 LED controller. This controller
  65. is connected via I2C. So I2C needs to be enabled.
  66. config PCA9551_I2C_ADDR
  67. hex "I2C address of PCA9551 LED controller"
  68. depends on PCA9551_LED
  69. default 0x60
  70. help
  71. The I2C address of the PCA9551 LED controller.
  72. config RESET
  73. bool "Enable support for reset drivers"
  74. depends on DM
  75. help
  76. Enable reset drivers which can be used to reset the CPU or board.
  77. Each driver can provide a reset method which will be called to
  78. effect a reset. The uclass will try all available drivers when
  79. reset_walk() is called.
  80. endmenu