Hi Rafael, On Fri, Jun 05, 2020 at 01:17:15PM +0200, Rafael J. Wysocki wrote: > > First off, GGL0001 is not a valid ACPI device ID, because the GGL prefix is not > present in the list at https://uefi.org/acpi_id_list > > There are two ways to address that. One would be to take the GOOG prefix > (present in the list above), append a proper unique number (if I were to > guess, I would say that 0001 had been reserved already) to it and then > put the resulting device ID into the firmware, to be returned _HID for the > device in question (you can add a _CID returning "GGL0001" so it can be > found by the old invalid ID at least from the kernel). This is not going to happen, as there are devices in the wild with such firmware (i.e. Samus - Google Pixel 2 - was shipped in 2015). Even if Google were to release updated firmware (which is quite unlikely), it does not mean that users who are not using Chrome OS would apply updated firmware. > The other one would > be to properly register the GGL prefix for Google and establish a process for > allocating IDs with that prefix internally. I think it depends on whether there are more instances of "GGL" prefix. I thought we mostly used GOOG for everything. Thanks. -- Dmitry
