312 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# Platform support for Chrome OS hardware (Chromebooks and Chromeboxes)4#5 6menuconfig CHROME_PLATFORMS7 bool "Platform support for Chrome hardware"8 depends on X86 || ARM || ARM64 || COMPILE_TEST9 help10 Say Y here to get to see options for platform support for11 various Chromebooks and Chromeboxes. This option alone does12 not add any kernel code.13 14 If you say N, all options in this submenu will be skipped and disabled.15 16if CHROME_PLATFORMS17 18config CHROMEOS_ACPI19 tristate "ChromeOS specific ACPI extensions"20 depends on ACPI21 help22 This driver provides the firmware interface for the services23 exported through the ChromeOS interfaces when using ChromeOS24 ACPI firmware.25 26 If you have an ACPI-compatible Chromebook, say Y or M here.27 The module will be called chromeos_acpi.28 29config CHROMEOS_LAPTOP30 tristate "Chrome OS Laptop"31 depends on I2C && DMI && X8632 help33 This driver instantiates i2c and smbus devices such as34 light sensors and touchpads.35 36 If you have a supported Chromebook, choose Y or M here.37 The module will be called chromeos_laptop.38 39config CHROMEOS_PSTORE40 tristate "Chrome OS pstore support"41 depends on X8642 help43 This module instantiates the persistent storage on x86 ChromeOS44 devices. It can be used to store away console logs and crash45 information across reboots.46 47 The range of memory used is 0xf00000-0x1000000, traditionally48 the memory used to back VGA controller memory.49 50 If you have a supported Chromebook, choose Y or M here.51 The module will be called chromeos_pstore.52 53config CHROMEOS_TBMC54 tristate "ChromeOS Tablet Switch Controller"55 depends on ACPI56 depends on INPUT57 help58 This option adds a driver for the tablet switch on59 select Chrome OS systems.60 61 To compile this driver as a module, choose M here: the62 module will be called chromeos_tbmc.63 64config CROS_EC65 tristate "ChromeOS Embedded Controller"66 select CROS_EC_PROTO67 depends on X86 || ARM || ARM64 || COMPILE_TEST68 help69 If you say Y here you get support for the ChromeOS Embedded70 Controller (EC) providing keyboard, battery and power services.71 You also need to enable the driver for the bus you are using. The72 protocol for talking to the EC is defined by the bus driver.73 74 To compile this driver as a module, choose M here: the75 module will be called cros_ec.76 77config CROS_EC_I2C78 tristate "ChromeOS Embedded Controller (I2C)"79 depends on CROS_EC && I2C80 81 help82 If you say Y here, you get support for talking to the ChromeOS83 EC through an I2C bus. This uses a simple byte-level protocol with84 a checksum. Failing accesses will be retried three times to85 improve reliability.86 87config CROS_EC_RPMSG88 tristate "ChromeOS Embedded Controller (rpmsg)"89 depends on CROS_EC && RPMSG && OF90 help91 If you say Y here, you get support for talking to the ChromeOS EC92 through rpmsg. This uses a simple byte-level protocol with a93 checksum. Also since there's no addition EC-to-host interrupt, this94 use a byte in message to distinguish host event from host command.95 96 To compile this driver as a module, choose M here: the97 module will be called cros_ec_rpmsg.98 99config CROS_EC_ISHTP100 tristate "ChromeOS Embedded Controller (ISHTP)"101 depends on CROS_EC102 depends on INTEL_ISH_HID103 help104 If you say Y here, you get support for talking to the ChromeOS EC105 firmware running on Intel Integrated Sensor Hub (ISH), using the106 ISH Transport protocol (ISH-TP). This uses a simple byte-level107 protocol with a checksum.108 109 To compile this driver as a module, choose M here: the110 module will be called cros_ec_ishtp.111 112config CROS_EC_SPI113 tristate "ChromeOS Embedded Controller (SPI)"114 depends on CROS_EC && SPI115 116 help117 If you say Y here, you get support for talking to the ChromeOS EC118 through a SPI bus, using a byte-level protocol. Since the EC's119 response time cannot be guaranteed, we support ignoring120 'pre-amble' bytes before the response actually starts.121 122config CROS_EC_UART123 tristate "ChromeOS Embedded Controller (UART)"124 depends on CROS_EC && ACPI && SERIAL_DEV_BUS125 help126 If you say Y here, you get support for talking to the ChromeOS EC127 through a UART, using a byte-level protocol.128 129 To compile this driver as a module, choose M here: the130 module will be called cros_ec_uart.131 132config CROS_EC_LPC133 tristate "ChromeOS Embedded Controller (LPC)"134 depends on CROS_EC && ACPI && (X86 || COMPILE_TEST)135 depends on HAS_IOPORT136 help137 If you say Y here, you get support for talking to the ChromeOS EC138 over an LPC bus, including the LPC Microchip EC (MEC) variant.139 This uses a simple byte-level protocol with a checksum. This is140 used for userspace access only. The kernel typically has its own141 communication methods.142 143 To compile this driver as a module, choose M here: the144 module will be called cros_ec_lpcs.145 146config CROS_EC_PROTO147 bool148 help149 ChromeOS EC communication protocol helpers.150 151config CROS_KBD_LED_BACKLIGHT152 tristate "Backlight LED support for Chrome OS keyboards"153 depends on LEDS_CLASS && (ACPI || CROS_EC || MFD_CROS_EC_DEV)154 help155 This option enables support for the keyboard backlight LEDs on156 select Chrome OS systems.157 158 To compile this driver as a module, choose M here: the159 module will be called cros_kbd_led_backlight.160 161config CROS_EC_CHARDEV162 tristate "ChromeOS EC miscdevice"163 depends on MFD_CROS_EC_DEV164 default MFD_CROS_EC_DEV165 help166 This driver adds file operations support to talk with the167 ChromeOS EC from userspace via a character device.168 169 To compile this driver as a module, choose M here: the170 module will be called cros_ec_chardev.171 172config CROS_EC_LIGHTBAR173 tristate "Chromebook Pixel's lightbar support"174 depends on MFD_CROS_EC_DEV175 default MFD_CROS_EC_DEV176 help177 This option exposes the Chromebook Pixel's lightbar to178 userspace.179 180 To compile this driver as a module, choose M here: the181 module will be called cros_ec_lightbar.182 183config CROS_EC_VBC184 tristate "ChromeOS EC vboot context support"185 depends on MFD_CROS_EC_DEV && OF186 default MFD_CROS_EC_DEV187 help188 This option exposes the ChromeOS EC vboot context nvram to189 userspace.190 191 To compile this driver as a module, choose M here: the192 module will be called cros_ec_vbc.193 194config CROS_EC_DEBUGFS195 tristate "Export ChromeOS EC internals in DebugFS"196 depends on MFD_CROS_EC_DEV && DEBUG_FS197 default MFD_CROS_EC_DEV198 help199 This option exposes the ChromeOS EC device internals to200 userspace.201 202 To compile this driver as a module, choose M here: the203 module will be called cros_ec_debugfs.204 205config CROS_EC_SENSORHUB206 tristate "ChromeOS EC MEMS Sensor Hub"207 depends on MFD_CROS_EC_DEV208 default MFD_CROS_EC_DEV209 help210 Allow loading IIO sensors. This driver is loaded by MFD and will in211 turn query the EC and register the sensors.212 It also spreads the sensor data coming from the EC to the IIO sensor213 object.214 215 To compile this driver as a module, choose M here: the216 module will be called cros_ec_sensorhub.217 218config CROS_EC_SYSFS219 tristate "ChromeOS EC control and information through sysfs"220 depends on MFD_CROS_EC_DEV && SYSFS221 default MFD_CROS_EC_DEV222 help223 This option exposes some sysfs attributes to control and get224 information from ChromeOS EC.225 226 To compile this driver as a module, choose M here: the227 module will be called cros_ec_sysfs.228 229config CROS_EC_TYPEC230 tristate "ChromeOS EC Type-C Connector Control"231 depends on MFD_CROS_EC_DEV && TYPEC232 depends on CROS_USBPD_NOTIFY233 depends on USB_ROLE_SWITCH234 default MFD_CROS_EC_DEV235 help236 If you say Y here, you get support for accessing Type C connector237 information from the Chrome OS EC.238 239 To compile this driver as a module, choose M here: the module will be240 called cros-ec-typec.241 242config CROS_HPS_I2C243 tristate "ChromeOS HPS device"244 depends on HID && I2C && PM245 help246 Say Y here if you want to enable support for the ChromeOS247 human presence sensor (HPS), attached via I2C. The driver supports a248 sensor connected to the I2C bus and exposes it as a character device.249 To save power, the sensor is automatically powered down when no250 clients are accessing it.251 252config CROS_USBPD_LOGGER253 tristate "Logging driver for USB PD charger"254 depends on CHARGER_CROS_USBPD255 default y256 select RTC_LIB257 help258 This option enables support for logging event data for the USB PD charger259 available in the Embedded Controller on ChromeOS systems.260 261 To compile this driver as a module, choose M here: the262 module will be called cros_usbpd_logger.263 264config CROS_USBPD_NOTIFY265 tristate "ChromeOS Type-C power delivery event notifier"266 depends on MFD_CROS_EC_DEV267 default MFD_CROS_EC_DEV268 help269 If you say Y here, you get support for Type-C PD event notifications270 from the ChromeOS EC. On ACPI platorms this driver will bind to the271 GOOG0003 ACPI device, and on platforms which don't have this device it272 will get initialized on ECs which support the feature273 EC_FEATURE_USB_PD.274 275 To compile this driver as a module, choose M here: the276 module will be called cros_usbpd_notify.277 278config CHROMEOS_PRIVACY_SCREEN279 tristate "ChromeOS Privacy Screen support"280 depends on ACPI281 depends on DRM282 select DRM_PRIVACY_SCREEN283 help284 This driver provides the support needed for the in-built electronic285 privacy screen that is present on some ChromeOS devices. When enabled,286 this should probably always be built into the kernel to avoid or287 minimize drm probe deferral.288 289config CROS_TYPEC_SWITCH290 tristate "ChromeOS EC Type-C Switch Control"291 depends on MFD_CROS_EC_DEV && TYPEC && ACPI292 default MFD_CROS_EC_DEV293 help294 If you say Y here, you get support for configuring the ChromeOS EC Type-C295 muxes and retimers.296 297 To compile this driver as a module, choose M here: the module will be298 called cros_typec_switch.299 300source "drivers/platform/chrome/wilco_ec/Kconfig"301 302# Kunit test cases303config CROS_KUNIT_EC_PROTO_TEST304 tristate "Kunit tests for ChromeOS EC protocol" if !KUNIT_ALL_TESTS305 depends on KUNIT && CROS_EC306 default KUNIT_ALL_TESTS307 select CROS_EC_PROTO308 help309 Kunit tests for ChromeOS EC protocol.310 311endif # CHROMEOS_PLATFORMS312