1 # SPDX-License-Identifier: GPL-2.0-only
3 # Platform support for Chrome OS hardware (Chromebooks and Chromeboxes)
6 menuconfig CHROME_PLATFORMS
7 bool "Platform support for Chrome hardware"
8 depends on X86 || ARM || ARM64 || COMPILE_TEST
10 Say Y here to get to see options for platform support for
11 various Chromebooks and Chromeboxes. This option alone does
12 not add any kernel code.
14 If you say N, all options in this submenu will be skipped and disabled.
19 tristate "ChromeOS specific ACPI extensions"
22 This driver provides the firmware interface for the services
23 exported through the ChromeOS interfaces when using ChromeOS
26 If you have an ACPI-compatible Chromebook, say Y or M here.
27 The module will be called chromeos_acpi.
29 config CHROMEOS_LAPTOP
30 tristate "Chrome OS Laptop"
31 depends on I2C && DMI && X86
33 This driver instantiates i2c and smbus devices such as
34 light sensors and touchpads.
36 If you have a supported Chromebook, choose Y or M here.
37 The module will be called chromeos_laptop.
39 config CHROMEOS_PSTORE
40 tristate "Chrome OS pstore support"
43 This module instantiates the persistent storage on x86 ChromeOS
44 devices. It can be used to store away console logs and crash
45 information across reboots.
47 The range of memory used is 0xf00000-0x1000000, traditionally
48 the memory used to back VGA controller memory.
50 If you have a supported Chromebook, choose Y or M here.
51 The module will be called chromeos_pstore.
54 tristate "ChromeOS Tablet Switch Controller"
58 This option adds a driver for the tablet switch on
59 select Chrome OS systems.
61 To compile this driver as a module, choose M here: the
62 module will be called chromeos_tbmc.
65 tristate "ChromeOS Embedded Controller"
67 depends on X86 || ARM || ARM64 || COMPILE_TEST
69 If you say Y here you get support for the ChromeOS Embedded
70 Controller (EC) providing keyboard, battery and power services.
71 You also need to enable the driver for the bus you are using. The
72 protocol for talking to the EC is defined by the bus driver.
74 To compile this driver as a module, choose M here: the
75 module will be called cros_ec.
78 tristate "ChromeOS Embedded Controller (I2C)"
79 depends on CROS_EC && I2C
82 If you say Y here, you get support for talking to the ChromeOS
83 EC through an I2C bus. This uses a simple byte-level protocol with
84 a checksum. Failing accesses will be retried three times to
88 tristate "ChromeOS Embedded Controller (rpmsg)"
89 depends on CROS_EC && RPMSG && OF
91 If you say Y here, you get support for talking to the ChromeOS EC
92 through rpmsg. This uses a simple byte-level protocol with a
93 checksum. Also since there's no addition EC-to-host interrupt, this
94 use a byte in message to distinguish host event from host command.
96 To compile this driver as a module, choose M here: the
97 module will be called cros_ec_rpmsg.
100 tristate "ChromeOS Embedded Controller (ISHTP)"
102 depends on INTEL_ISH_HID
104 If you say Y here, you get support for talking to the ChromeOS EC
105 firmware running on Intel Integrated Sensor Hub (ISH), using the
106 ISH Transport protocol (ISH-TP). This uses a simple byte-level
107 protocol with a checksum.
109 To compile this driver as a module, choose M here: the
110 module will be called cros_ec_ishtp.
113 tristate "ChromeOS Embedded Controller (SPI)"
114 depends on CROS_EC && SPI
117 If you say Y here, you get support for talking to the ChromeOS EC
118 through a SPI bus, using a byte-level protocol. Since the EC's
119 response time cannot be guaranteed, we support ignoring
120 'pre-amble' bytes before the response actually starts.
123 tristate "ChromeOS Embedded Controller (UART)"
124 depends on CROS_EC && ACPI && SERIAL_DEV_BUS
126 If you say Y here, you get support for talking to the ChromeOS EC
127 through a UART, using a byte-level protocol.
129 To compile this driver as a module, choose M here: the
130 module will be called cros_ec_uart.
133 tristate "ChromeOS Embedded Controller (LPC)"
134 depends on CROS_EC && ACPI && (X86 || COMPILE_TEST)
135 depends on HAS_IOPORT
137 If you say Y here, you get support for talking to the ChromeOS EC
138 over an LPC bus, including the LPC Microchip EC (MEC) variant.
139 This uses a simple byte-level protocol with a checksum. This is
140 used for userspace access only. The kernel typically has its own
141 communication methods.
143 To compile this driver as a module, choose M here: the
144 module will be called cros_ec_lpcs.
149 ChromeOS EC communication protocol helpers.
151 config CROS_KBD_LED_BACKLIGHT
152 tristate "Backlight LED support for Chrome OS keyboards"
153 depends on LEDS_CLASS && (ACPI || CROS_EC || MFD_CROS_EC_DEV)
155 This option enables support for the keyboard backlight LEDs on
156 select Chrome OS systems.
158 To compile this driver as a module, choose M here: the
159 module will be called cros_kbd_led_backlight.
161 config CROS_EC_CHARDEV
162 tristate "ChromeOS EC miscdevice"
163 depends on MFD_CROS_EC_DEV
164 default MFD_CROS_EC_DEV
166 This driver adds file operations support to talk with the
167 ChromeOS EC from userspace via a character device.
169 To compile this driver as a module, choose M here: the
170 module will be called cros_ec_chardev.
172 config CROS_EC_LIGHTBAR
173 tristate "Chromebook Pixel's lightbar support"
174 depends on MFD_CROS_EC_DEV
175 default MFD_CROS_EC_DEV
177 This option exposes the Chromebook Pixel's lightbar to
180 To compile this driver as a module, choose M here: the
181 module will be called cros_ec_lightbar.
184 tristate "ChromeOS EC vboot context support"
185 depends on MFD_CROS_EC_DEV && OF
186 default MFD_CROS_EC_DEV
188 This option exposes the ChromeOS EC vboot context nvram to
191 To compile this driver as a module, choose M here: the
192 module will be called cros_ec_vbc.
194 config CROS_EC_DEBUGFS
195 tristate "Export ChromeOS EC internals in DebugFS"
196 depends on MFD_CROS_EC_DEV && DEBUG_FS
197 default MFD_CROS_EC_DEV
199 This option exposes the ChromeOS EC device internals to
202 To compile this driver as a module, choose M here: the
203 module will be called cros_ec_debugfs.
205 config CROS_EC_SENSORHUB
206 tristate "ChromeOS EC MEMS Sensor Hub"
207 depends on MFD_CROS_EC_DEV
208 default MFD_CROS_EC_DEV
210 Allow loading IIO sensors. This driver is loaded by MFD and will in
211 turn query the EC and register the sensors.
212 It also spreads the sensor data coming from the EC to the IIO sensor
215 To compile this driver as a module, choose M here: the
216 module will be called cros_ec_sensorhub.
219 tristate "ChromeOS EC control and information through sysfs"
220 depends on MFD_CROS_EC_DEV && SYSFS
221 default MFD_CROS_EC_DEV
223 This option exposes some sysfs attributes to control and get
224 information from ChromeOS EC.
226 To compile this driver as a module, choose M here: the
227 module will be called cros_ec_sysfs.
230 tristate "ChromeOS EC Type-C Connector Control"
231 depends on MFD_CROS_EC_DEV && TYPEC
232 depends on CROS_USBPD_NOTIFY
233 depends on USB_ROLE_SWITCH
234 default MFD_CROS_EC_DEV
236 If you say Y here, you get support for accessing Type C connector
237 information from the Chrome OS EC.
239 To compile this driver as a module, choose M here: the module will be
240 called cros-ec-typec.
243 tristate "ChromeOS HPS device"
244 depends on HID && I2C && PM
246 Say Y here if you want to enable support for the ChromeOS
247 human presence sensor (HPS), attached via I2C. The driver supports a
248 sensor connected to the I2C bus and exposes it as a character device.
249 To save power, the sensor is automatically powered down when no
250 clients are accessing it.
252 config CROS_USBPD_LOGGER
253 tristate "Logging driver for USB PD charger"
254 depends on CHARGER_CROS_USBPD
258 This option enables support for logging event data for the USB PD charger
259 available in the Embedded Controller on ChromeOS systems.
261 To compile this driver as a module, choose M here: the
262 module will be called cros_usbpd_logger.
264 config CROS_USBPD_NOTIFY
265 tristate "ChromeOS Type-C power delivery event notifier"
266 depends on MFD_CROS_EC_DEV
267 default MFD_CROS_EC_DEV
269 If you say Y here, you get support for Type-C PD event notifications
270 from the ChromeOS EC. On ACPI platorms this driver will bind to the
271 GOOG0003 ACPI device, and on platforms which don't have this device it
272 will get initialized on ECs which support the feature
275 To compile this driver as a module, choose M here: the
276 module will be called cros_usbpd_notify.
278 config CHROMEOS_PRIVACY_SCREEN
279 tristate "ChromeOS Privacy Screen support"
282 select DRM_PRIVACY_SCREEN
284 This driver provides the support needed for the in-built electronic
285 privacy screen that is present on some ChromeOS devices. When enabled,
286 this should probably always be built into the kernel to avoid or
287 minimize drm probe deferral.
289 config CROS_TYPEC_SWITCH
290 tristate "ChromeOS EC Type-C Switch Control"
291 depends on MFD_CROS_EC_DEV && TYPEC && ACPI
292 default MFD_CROS_EC_DEV
294 If you say Y here, you get support for configuring the ChromeOS EC Type-C
297 To compile this driver as a module, choose M here: the module will be
298 called cros_typec_switch.
300 source "drivers/platform/chrome/wilco_ec/Kconfig"
303 config CROS_KUNIT_EC_PROTO_TEST
304 tristate "Kunit tests for ChromeOS EC protocol" if !KUNIT_ALL_TESTS
305 depends on KUNIT && CROS_EC
306 default KUNIT_ALL_TESTS
309 Kunit tests for ChromeOS EC protocol.
311 endif # CHROMEOS_PLATFORMS