Searched full:chrome (Results 1 – 25 of 57) sorted by relevance
123
4 Chrome OS ACPI Device7 Hardware functionality specific to Chrome OS is exposed through a Chrome OS ACPI device.8 The plug and play ID of a Chrome OS ACPI device is GGL0001 and the hardware ID is19 - Chrome OS switch positions22 - Chrome OS hardware ID25 - Chrome OS firmware version28 - Chrome OS read-only firmware version31 - Chrome OS boot information34 - Chrome OS GPIO assignments37 - Chrome OS NVRAM locations[all …]
3 * sc7280 fragment for devices with Chrome bootloader6 * place by the Chrome bootloader which are different than what's put into8 * things that will hold true for any conceivable Chrome design17 * required by the setup for Chrome boards.79 /* The PMIC PON code isn't compatible w/ how Chrome EC/BIOS handle things. */85 * Chrome designs always boot from SPI flash hooked up to the qspi.162 /* PINCTRL - chrome-common pinctrl */
7 /* Modem setup is different on Chrome setups than typical Qualcomm setup */
3 # Platform support for Chrome OS hardware (Chromebooks and Chromeboxes)7 bool "Platform support for Chrome hardware"30 tristate "Chrome OS Laptop"40 tristate "Chrome OS pstore support"59 select Chrome OS systems.152 tristate "Backlight LED support for Chrome OS keyboards"156 select Chrome OS systems.237 information from the Chrome OS EC.300 source "drivers/platform/chrome/wilco_ec/Kconfig"
30 /* Platform-specific data for the Chrome OS EC Type C controller. */
4 $id: http://devicetree.org/schemas/chrome/google,cros-ec-typec.yaml#7 title: Google Chrome OS EC(Embedded Controller) Type C port driver.14 Chrome OS devices have an Embedded Controller(EC) which has access to
4 $id: http://devicetree.org/schemas/chrome/google,cros-kbd-led-backlight.yaml#
17 devices depending on the platform. On machines designed for Chrome OS22 If your device was designed for Chrome OS, this driver will provide
102 $ref: /schemas/chrome/google,cros-ec-typec.yaml#112 $ref: /schemas/chrome/google,cros-kbd-led-backlight.yaml#145 to a Chrome OS tablet. This device cannot be detected at runtime.
87 * RECOVERY_SW_L is Chrome OS ABI. Schematics call243 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
95 * RECOVERY_SW_L is Chrome OS ABI. Schematics call251 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
147 * RECOVERY_SW_L is Chrome OS ABI. Schematics call308 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
217 * RECOVERY_SW_L is Chrome OS ABI. Schematics call388 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
275 * RECOVERY_SW_L is Chrome OS ABI. Schematics call375 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
8 source "drivers/platform/chrome/Kconfig"
12 obj-$(CONFIG_CHROME_PLATFORMS) += chrome/
9 named :chrome
3 # Chrome OS Embedded Controller managed sensors library
3 * cros_ec_sensors - Driver for Chrome OS Embedded Controller sensors.7 * This driver uses the cros-ec interface to communicate with the Chrome OS
8 * This driver uses the cros-ec interface to communicate with the Chrome OS
32 Returns switch position for Chrome OS specific hardware72 Returns type of the GPIO signal for the Chrome OS specific
5 As part of Chrome OS's FAFT (Fully Automated Firmware Testing)
3 * Driver for older Chrome OS EC accelerometer8 * with the Chrome OS EC about accelerometer data or older commands.
131 - Chrome browser: protect some security sensitive data structures.181 CFI [4]. Chrome browser in ChromeOS will be the first user of this API.
11 for linux or chrome platform for data exchange over PCIe interface between