Kconfig 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Platform support for Chrome OS hardware (Chromebooks and Chromeboxes)
  4. #
  5. menuconfig CHROME_PLATFORMS
  6. bool "Platform support for Chrome hardware"
  7. depends on X86 || ARM || ARM64 || COMPILE_TEST
  8. help
  9. Say Y here to get to see options for platform support for
  10. various Chromebooks and Chromeboxes. This option alone does
  11. not add any kernel code.
  12. If you say N, all options in this submenu will be skipped and disabled.
  13. if CHROME_PLATFORMS
  14. config CHROMEOS_ACPI
  15. tristate "ChromeOS specific ACPI extensions"
  16. depends on ACPI
  17. help
  18. This driver provides the firmware interface for the services
  19. exported through the ChromeOS interfaces when using ChromeOS
  20. ACPI firmware.
  21. If you have an ACPI-compatible Chromebook, say Y or M here.
  22. The module will be called chromeos_acpi.
  23. config CHROMEOS_LAPTOP
  24. tristate "Chrome OS Laptop"
  25. depends on I2C && DMI && X86
  26. help
  27. This driver instantiates i2c and smbus devices such as
  28. light sensors and touchpads.
  29. If you have a supported Chromebook, choose Y or M here.
  30. The module will be called chromeos_laptop.
  31. config CHROMEOS_PSTORE
  32. tristate "Chrome OS pstore support"
  33. depends on X86
  34. help
  35. This module instantiates the persistent storage on x86 ChromeOS
  36. devices. It can be used to store away console logs and crash
  37. information across reboots.
  38. The range of memory used is 0xf00000-0x1000000, traditionally
  39. the memory used to back VGA controller memory.
  40. If you have a supported Chromebook, choose Y or M here.
  41. The module will be called chromeos_pstore.
  42. config CHROMEOS_TBMC
  43. tristate "ChromeOS Tablet Switch Controller"
  44. depends on ACPI
  45. depends on INPUT
  46. help
  47. This option adds a driver for the tablet switch on
  48. select Chrome OS systems.
  49. To compile this driver as a module, choose M here: the
  50. module will be called chromeos_tbmc.
  51. config CROS_EC
  52. tristate "ChromeOS Embedded Controller"
  53. select CROS_EC_PROTO
  54. depends on X86 || ARM || ARM64 || COMPILE_TEST
  55. help
  56. If you say Y here you get support for the ChromeOS Embedded
  57. Controller (EC) providing keyboard, battery and power services.
  58. You also need to enable the driver for the bus you are using. The
  59. protocol for talking to the EC is defined by the bus driver.
  60. To compile this driver as a module, choose M here: the
  61. module will be called cros_ec.
  62. config CROS_EC_I2C
  63. tristate "ChromeOS Embedded Controller (I2C)"
  64. depends on CROS_EC && I2C
  65. help
  66. If you say Y here, you get support for talking to the ChromeOS
  67. EC through an I2C bus. This uses a simple byte-level protocol with
  68. a checksum. Failing accesses will be retried three times to
  69. improve reliability.
  70. config CROS_EC_RPMSG
  71. tristate "ChromeOS Embedded Controller (rpmsg)"
  72. depends on CROS_EC && RPMSG && OF
  73. help
  74. If you say Y here, you get support for talking to the ChromeOS EC
  75. through rpmsg. This uses a simple byte-level protocol with a
  76. checksum. Also since there's no addition EC-to-host interrupt, this
  77. use a byte in message to distinguish host event from host command.
  78. To compile this driver as a module, choose M here: the
  79. module will be called cros_ec_rpmsg.
  80. config CROS_EC_ISHTP
  81. tristate "ChromeOS Embedded Controller (ISHTP)"
  82. depends on CROS_EC
  83. depends on INTEL_ISH_HID
  84. help
  85. If you say Y here, you get support for talking to the ChromeOS EC
  86. firmware running on Intel Integrated Sensor Hub (ISH), using the
  87. ISH Transport protocol (ISH-TP). This uses a simple byte-level
  88. protocol with a checksum.
  89. To compile this driver as a module, choose M here: the
  90. module will be called cros_ec_ishtp.
  91. config CROS_EC_SPI
  92. tristate "ChromeOS Embedded Controller (SPI)"
  93. depends on CROS_EC && SPI
  94. help
  95. If you say Y here, you get support for talking to the ChromeOS EC
  96. through a SPI bus, using a byte-level protocol. Since the EC's
  97. response time cannot be guaranteed, we support ignoring
  98. 'pre-amble' bytes before the response actually starts.
  99. config CROS_EC_LPC
  100. tristate "ChromeOS Embedded Controller (LPC)"
  101. depends on CROS_EC && ACPI && (X86 || COMPILE_TEST)
  102. help
  103. If you say Y here, you get support for talking to the ChromeOS EC
  104. over an LPC bus, including the LPC Microchip EC (MEC) variant.
  105. This uses a simple byte-level protocol with a checksum. This is
  106. used for userspace access only. The kernel typically has its own
  107. communication methods.
  108. To compile this driver as a module, choose M here: the
  109. module will be called cros_ec_lpcs.
  110. config CROS_EC_PROTO
  111. bool
  112. help
  113. ChromeOS EC communication protocol helpers.
  114. config CROS_KBD_LED_BACKLIGHT
  115. tristate "Backlight LED support for Chrome OS keyboards"
  116. depends on LEDS_CLASS && (ACPI || CROS_EC)
  117. help
  118. This option enables support for the keyboard backlight LEDs on
  119. select Chrome OS systems.
  120. To compile this driver as a module, choose M here: the
  121. module will be called cros_kbd_led_backlight.
  122. config CROS_EC_CHARDEV
  123. tristate "ChromeOS EC miscdevice"
  124. depends on MFD_CROS_EC_DEV
  125. default MFD_CROS_EC_DEV
  126. help
  127. This driver adds file operations support to talk with the
  128. ChromeOS EC from userspace via a character device.
  129. To compile this driver as a module, choose M here: the
  130. module will be called cros_ec_chardev.
  131. config CROS_EC_LIGHTBAR
  132. tristate "Chromebook Pixel's lightbar support"
  133. depends on MFD_CROS_EC_DEV
  134. default MFD_CROS_EC_DEV
  135. help
  136. This option exposes the Chromebook Pixel's lightbar to
  137. userspace.
  138. To compile this driver as a module, choose M here: the
  139. module will be called cros_ec_lightbar.
  140. config CROS_EC_VBC
  141. tristate "ChromeOS EC vboot context support"
  142. depends on MFD_CROS_EC_DEV && OF
  143. default MFD_CROS_EC_DEV
  144. help
  145. This option exposes the ChromeOS EC vboot context nvram to
  146. userspace.
  147. To compile this driver as a module, choose M here: the
  148. module will be called cros_ec_vbc.
  149. config CROS_EC_DEBUGFS
  150. tristate "Export ChromeOS EC internals in DebugFS"
  151. depends on MFD_CROS_EC_DEV && DEBUG_FS
  152. default MFD_CROS_EC_DEV
  153. help
  154. This option exposes the ChromeOS EC device internals to
  155. userspace.
  156. To compile this driver as a module, choose M here: the
  157. module will be called cros_ec_debugfs.
  158. config CROS_EC_SENSORHUB
  159. tristate "ChromeOS EC MEMS Sensor Hub"
  160. depends on MFD_CROS_EC_DEV
  161. default MFD_CROS_EC_DEV
  162. help
  163. Allow loading IIO sensors. This driver is loaded by MFD and will in
  164. turn query the EC and register the sensors.
  165. It also spreads the sensor data coming from the EC to the IIO sensor
  166. object.
  167. To compile this driver as a module, choose M here: the
  168. module will be called cros_ec_sensorhub.
  169. config CROS_EC_SYSFS
  170. tristate "ChromeOS EC control and information through sysfs"
  171. depends on MFD_CROS_EC_DEV && SYSFS
  172. default MFD_CROS_EC_DEV
  173. help
  174. This option exposes some sysfs attributes to control and get
  175. information from ChromeOS EC.
  176. To compile this driver as a module, choose M here: the
  177. module will be called cros_ec_sysfs.
  178. config CROS_EC_TYPEC
  179. tristate "ChromeOS EC Type-C Connector Control"
  180. depends on MFD_CROS_EC_DEV && TYPEC
  181. depends on CROS_USBPD_NOTIFY
  182. depends on USB_ROLE_SWITCH
  183. default MFD_CROS_EC_DEV
  184. help
  185. If you say Y here, you get support for accessing Type C connector
  186. information from the Chrome OS EC.
  187. To compile this driver as a module, choose M here: the module will be
  188. called cros_ec_typec.
  189. config CROS_USBPD_LOGGER
  190. tristate "Logging driver for USB PD charger"
  191. depends on CHARGER_CROS_USBPD
  192. default y
  193. select RTC_LIB
  194. help
  195. This option enables support for logging event data for the USB PD charger
  196. available in the Embedded Controller on ChromeOS systems.
  197. To compile this driver as a module, choose M here: the
  198. module will be called cros_usbpd_logger.
  199. config CROS_USBPD_NOTIFY
  200. tristate "ChromeOS Type-C power delivery event notifier"
  201. depends on MFD_CROS_EC_DEV
  202. default MFD_CROS_EC_DEV
  203. help
  204. If you say Y here, you get support for Type-C PD event notifications
  205. from the ChromeOS EC. On ACPI platorms this driver will bind to the
  206. GOOG0003 ACPI device, and on platforms which don't have this device it
  207. will get initialized on ECs which support the feature
  208. EC_FEATURE_USB_PD.
  209. To compile this driver as a module, choose M here: the
  210. module will be called cros_usbpd_notify.
  211. config CHROMEOS_PRIVACY_SCREEN
  212. tristate "ChromeOS Privacy Screen support"
  213. depends on ACPI
  214. depends on DRM
  215. select DRM_PRIVACY_SCREEN
  216. help
  217. This driver provides the support needed for the in-built electronic
  218. privacy screen that is present on some ChromeOS devices. When enabled,
  219. this should probably always be built into the kernel to avoid or
  220. minimize drm probe deferral.
  221. config CROS_TYPEC_SWITCH
  222. tristate "ChromeOS EC Type-C Switch Control"
  223. depends on MFD_CROS_EC_DEV && TYPEC && ACPI
  224. default MFD_CROS_EC_DEV
  225. help
  226. If you say Y here, you get support for configuring the ChromeOS EC Type-C
  227. muxes and retimers.
  228. To compile this driver as a module, choose M here: the module will be
  229. called cros_typec_switch.
  230. source "drivers/platform/chrome/wilco_ec/Kconfig"
  231. # Kunit test cases
  232. config CROS_KUNIT
  233. tristate "Kunit tests for ChromeOS" if !KUNIT_ALL_TESTS
  234. depends on KUNIT && CROS_EC
  235. default KUNIT_ALL_TESTS
  236. select CROS_EC_PROTO
  237. help
  238. ChromeOS Kunit tests.
  239. endif # CHROMEOS_PLATFORMS