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.
18 config CHROMEOS_LAPTOP
19 tristate "Chrome OS Laptop"
20 depends on I2C && DMI && X86
22 This driver instantiates i2c and smbus devices such as
23 light sensors and touchpads.
25 If you have a supported Chromebook, choose Y or M here.
26 The module will be called chromeos_laptop.
28 config CHROMEOS_PSTORE
29 tristate "Chrome OS pstore support"
32 This module instantiates the persistent storage on x86 ChromeOS
33 devices. It can be used to store away console logs and crash
34 information across reboots.
36 The range of memory used is 0xf00000-0x1000000, traditionally
37 the memory used to back VGA controller memory.
39 If you have a supported Chromebook, choose Y or M here.
40 The module will be called chromeos_pstore.
43 tristate "ChromeOS Tablet Switch Controller"
47 This option adds a driver for the tablet switch on
48 select Chrome OS systems.
50 To compile this driver as a module, choose M here: the
51 module will be called chromeos_tbmc.
54 tristate "ChromeOS Embedded Controller"
56 depends on X86 || ARM || ARM64 || COMPILE_TEST
58 If you say Y here you get support for the ChromeOS Embedded
59 Controller (EC) providing keyboard, battery and power services.
60 You also need to enable the driver for the bus you are using. The
61 protocol for talking to the EC is defined by the bus driver.
63 To compile this driver as a module, choose M here: the
64 module will be called cros_ec.
67 tristate "ChromeOS Embedded Controller (I2C)"
68 depends on CROS_EC && I2C
71 If you say Y here, you get support for talking to the ChromeOS
72 EC through an I2C bus. This uses a simple byte-level protocol with
73 a checksum. Failing accesses will be retried three times to
77 tristate "ChromeOS Embedded Controller (rpmsg)"
78 depends on CROS_EC && RPMSG && OF
80 If you say Y here, you get support for talking to the ChromeOS EC
81 through rpmsg. This uses a simple byte-level protocol with a
82 checksum. Also since there's no addition EC-to-host interrupt, this
83 use a byte in message to distinguish host event from host command.
85 To compile this driver as a module, choose M here: the
86 module will be called cros_ec_rpmsg.
89 tristate "ChromeOS Embedded Controller (ISHTP)"
91 depends on INTEL_ISH_HID
93 If you say Y here, you get support for talking to the ChromeOS EC
94 firmware running on Intel Integrated Sensor Hub (ISH), using the
95 ISH Transport protocol (ISH-TP). This uses a simple byte-level
96 protocol with a checksum.
98 To compile this driver as a module, choose M here: the
99 module will be called cros_ec_ishtp.
102 tristate "ChromeOS Embedded Controller (SPI)"
103 depends on CROS_EC && SPI
106 If you say Y here, you get support for talking to the ChromeOS EC
107 through a SPI bus, using a byte-level protocol. Since the EC's
108 response time cannot be guaranteed, we support ignoring
109 'pre-amble' bytes before the response actually starts.
112 tristate "ChromeOS Embedded Controller (LPC)"
113 depends on CROS_EC && ACPI && (X86 || COMPILE_TEST)
115 If you say Y here, you get support for talking to the ChromeOS EC
116 over an LPC bus, including the LPC Microchip EC (MEC) variant.
117 This uses a simple byte-level protocol with a checksum. This is
118 used for userspace access only. The kernel typically has its own
119 communication methods.
121 To compile this driver as a module, choose M here: the
122 module will be called cros_ec_lpcs.
127 ChromeOS EC communication protocol helpers.
129 config CROS_KBD_LED_BACKLIGHT
130 tristate "Backlight LED support for Chrome OS keyboards"
131 depends on LEDS_CLASS && ACPI
133 This option enables support for the keyboard backlight LEDs on
134 select Chrome OS systems.
136 To compile this driver as a module, choose M here: the
137 module will be called cros_kbd_led_backlight.
139 config CROS_EC_CHARDEV
140 tristate "ChromeOS EC miscdevice"
141 depends on MFD_CROS_EC_DEV
142 default MFD_CROS_EC_DEV
144 This driver adds file operations support to talk with the
145 ChromeOS EC from userspace via a character device.
147 To compile this driver as a module, choose M here: the
148 module will be called cros_ec_chardev.
150 config CROS_EC_LIGHTBAR
151 tristate "Chromebook Pixel's lightbar support"
152 depends on MFD_CROS_EC_DEV
153 default MFD_CROS_EC_DEV
155 This option exposes the Chromebook Pixel's lightbar to
158 To compile this driver as a module, choose M here: the
159 module will be called cros_ec_lightbar.
162 tristate "ChromeOS EC vboot context support"
163 depends on MFD_CROS_EC_DEV && OF
164 default MFD_CROS_EC_DEV
166 This option exposes the ChromeOS EC vboot context nvram to
169 To compile this driver as a module, choose M here: the
170 module will be called cros_ec_vbc.
172 config CROS_EC_DEBUGFS
173 tristate "Export ChromeOS EC internals in DebugFS"
174 depends on MFD_CROS_EC_DEV && DEBUG_FS
175 default MFD_CROS_EC_DEV
177 This option exposes the ChromeOS EC device internals to
180 To compile this driver as a module, choose M here: the
181 module will be called cros_ec_debugfs.
183 config CROS_EC_SENSORHUB
184 tristate "ChromeOS EC MEMS Sensor Hub"
185 depends on MFD_CROS_EC_DEV
186 default MFD_CROS_EC_DEV
188 Allow loading IIO sensors. This driver is loaded by MFD and will in
189 turn query the EC and register the sensors.
190 It also spreads the sensor data coming from the EC to the IIO sensor
193 To compile this driver as a module, choose M here: the
194 module will be called cros_ec_sensorhub.
197 tristate "ChromeOS EC control and information through sysfs"
198 depends on MFD_CROS_EC_DEV && SYSFS
199 default MFD_CROS_EC_DEV
201 This option exposes some sysfs attributes to control and get
202 information from ChromeOS EC.
204 To compile this driver as a module, choose M here: the
205 module will be called cros_ec_sysfs.
208 tristate "ChromeOS EC Type-C Connector Control"
209 depends on MFD_CROS_EC_DEV && TYPEC
210 depends on CROS_USBPD_NOTIFY
211 depends on USB_ROLE_SWITCH
212 default MFD_CROS_EC_DEV
214 If you say Y here, you get support for accessing Type C connector
215 information from the Chrome OS EC.
217 To compile this driver as a module, choose M here: the module will be
218 called cros_ec_typec.
220 config CROS_USBPD_LOGGER
221 tristate "Logging driver for USB PD charger"
222 depends on CHARGER_CROS_USBPD
226 This option enables support for logging event data for the USB PD charger
227 available in the Embedded Controller on ChromeOS systems.
229 To compile this driver as a module, choose M here: the
230 module will be called cros_usbpd_logger.
232 config CROS_USBPD_NOTIFY
233 tristate "ChromeOS Type-C power delivery event notifier"
234 depends on MFD_CROS_EC_DEV
235 default MFD_CROS_EC_DEV
237 If you say Y here, you get support for Type-C PD event notifications
238 from the ChromeOS EC. On ACPI platorms this driver will bind to the
239 GOOG0003 ACPI device, and on platforms which don't have this device it
240 will get initialized on ECs which support the feature
243 To compile this driver as a module, choose M here: the
244 module will be called cros_usbpd_notify.
246 source "drivers/platform/chrome/wilco_ec/Kconfig"
248 endif # CHROMEOS_PLATFORMS