1 .. SPDX-License-Identifier: GPL-2.0
7 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 is
9 GOOG0016. The following ACPI objects are supported:
11 .. flat-table:: Supported ACPI Objects
19 - Chrome OS switch positions
22 - Chrome OS hardware ID
25 - Chrome OS firmware version
28 - Chrome OS read-only firmware version
31 - Chrome OS boot information
34 - Chrome OS GPIO assignments
37 - Chrome OS NVRAM locations
40 - Chrome OS verified boot data
43 - Chrome OS flashmap base address
46 - Chrome OS method list
48 CHSW (Chrome OS switch positions)
49 =================================
50 This control method returns the switch positions for Chrome OS specific hardware switches.
58 An integer containing the switch positions as bitfields:
64 - Recovery button was pressed when x86 firmware booted.
67 - Recovery button was pressed when EC firmware booted. (required if EC EEPROM is
68 rewritable; otherwise optional)
71 - Developer switch was enabled when x86 firmware booted.
74 - Firmware write protection was disabled when x86 firmware booted. (required if
75 firmware write protection is controlled through x86 BIOS; otherwise optional)
77 All other bits are reserved and should be set to 0.
79 HWID (Chrome OS hardware ID)
80 ============================
81 This control method returns the hardware ID for the Chromebook.
89 A null-terminated ASCII string containing the hardware ID from the Model-Specific Data area of
92 Note that the hardware ID can be up to 256 characters long, including the terminating null.
94 FWID (Chrome OS firmware version)
95 =================================
96 This control method returns the firmware version for the rewritable portion of the main
105 A null-terminated ASCII string containing the complete firmware version for the rewritable
106 portion of the main processor firmware.
108 FRID (Chrome OS read-only firmware version)
109 ===========================================
110 This control method returns the firmware version for the read-only portion of the main
119 A null-terminated ASCII string containing the complete firmware version for the read-only
120 (bootstrap + recovery ) portion of the main processor firmware.
122 BINF (Chrome OS boot information)
123 =================================
124 This control method returns information about the current boot.
139 Active Main Firmware Type
153 - Set to 256 (0x100). This indicates this field is no longer used.
157 - Set to 256 (0x100). This indicates this field is no longer used.
159 * - Active EC firmware
161 - The EC firmware which was used during boot.
163 - 0 - Read-only (recovery) firmware
164 - 1 - Rewritable firmware.
166 Set to 0 if EC firmware is always read-only.
168 * - Active Main Firmware Type
170 - The main firmware type which was used during boot.
175 - 3 - netboot (factory installation only)
177 Other values are reserved.
181 - Set to 256 (0x100). This indicates this field is no longer used.
183 GPIO (Chrome OS GPIO assignments)
184 =================================
185 This control method returns information about Chrome OS specific GPIO assignments for
186 Chrome OS hardware, so the kernel can directly control that hardware.
198 // First GPIO assignment
201 Controller Offset //DWORD
202 Controller Name //ASCIIZ
206 // Last GPIO assignment
209 Controller Offset //DWORD
210 Controller Name //ASCIIZ
214 Where ASCIIZ means a null-terminated ASCII string.
226 - Type of GPIO signal
228 - 0x00000001 - Recovery button
229 - 0x00000002 - Developer mode switch
230 - 0x00000003 - Firmware write protection switch
231 - 0x00000100 - Debug header GPIO 0
233 - 0x000001FF - Debug header GPIO 255
235 Other values are reserved.
239 - Signal attributes as bitfields:
241 - 0x00000001 - Signal is active-high (for button, a GPIO value
242 of 1 means the button is pressed; for switches, a GPIO value
243 of 1 means the switch is enabled). If this bit is 0, the signal
244 is active low. Set to 0 for debug header GPIOs.
246 * - Controller Offset
248 - GPIO number on the specified controller.
252 - Name of the controller for the GPIO.
253 Currently supported names:
254 "NM10" - Intel NM10 chip
256 VBNV (Chrome OS NVRAM locations)
257 ================================
258 This control method returns information about the NVRAM (CMOS) locations used to
259 communicate with the BIOS.
270 NV Storage Block Offset //DWORD
271 NV Storage Block Size //DWORD
282 * - NV Storage Block Offset
284 - Offset in CMOS bank 0 of the verified boot non-volatile storage block, counting from
285 the first writable CMOS byte (that is, offset=0 is the byte following the 14 bytes of
288 * - NV Storage Block Size
290 - Size in bytes of the verified boot non-volatile storage block.
292 FMAP (Chrome OS flashmap address)
293 =================================
294 This control method returns the physical memory address of the start of the main processor
303 A DWORD containing the physical memory address of the start of the main processor firmware
306 VDTA (Chrome OS verified boot data)
307 ===================================
308 This control method returns the verified boot data block shared between the firmware
309 verification step and the kernel verification step.
317 A buffer containing the verified boot data block.
319 MECK (Management Engine Checksum)
320 =================================
321 This control method returns the SHA-1 or SHA-256 hash that is read out of the Management
322 Engine extended registers during boot. The hash is exported via ACPI so the OS can verify that
323 the ME firmware has not changed. If Management Engine is not present, or if the firmware was
324 unable to read the extended registers, this buffer can be zero.
332 A buffer containing the ME hash.
334 MLST (Chrome OS method list)
335 ============================
336 This control method returns a list of the other control methods supported by the Chrome OS
345 A package containing a list of null-terminated ASCII strings, one for each control method
346 supported by the Chrome OS hardware device, not including the MLST method itself.
347 For this version of the specification, the result is: