3  * Module Name: evgpeinit - System GPE initialization and update
165  * Originally (2000 - 2010), the GPE initialization code performed a walk of
187  * DESCRIPTION: Initialize the GPE data structures and the FADT GPE 0/1 blocks
214      * Initialize the GPE Block(s) defined in the FADT  in AcpiEvGpeInitialize()
216      * Why the GPE register block lengths are divided by 2:  From the ACPI  in AcpiEvGpeInitialize()
230      * Determine the maximum GPE number for this machine.  in AcpiEvGpeInitialize()
241         /* GPE block 0 exists (has both length and address > 0) */  in AcpiEvGpeInitialize()
246         /* Install GPE Block 0 */  in AcpiEvGpeInitialize()
257                 "Could not create GPE Block 0"));  in AcpiEvGpeInitialize()
264         /* GPE block 1 exists (has both length and address > 0) */  in AcpiEvGpeInitialize()
274                 "GPE0 block (GPE 0 to %u) overlaps the GPE1 block "  in AcpiEvGpeInitialize()
275                 "(GPE %u to %u) - Ignoring GPE1",  in AcpiEvGpeInitialize()
286             /* Install GPE Block 1 */  in AcpiEvGpeInitialize()
298                     "Could not create GPE Block 1"));  in AcpiEvGpeInitialize()
302              * GPE0 and GPE1 do not have to be contiguous in the GPE number  in AcpiEvGpeInitialize()
303              * space. However, GPE0 always starts at GPE number zero.  in AcpiEvGpeInitialize()
308     /* Exit if there are no GPE registers */  in AcpiEvGpeInitialize()
315             "There are no GPE blocks defined in the FADT\n"));  in AcpiEvGpeInitialize()
334  * DESCRIPTION: Check for new GPE methods (_Lxx/_Exx) made available as a
335  *              result of a Load() or LoadTable() operation. If new GPE
351      * Find any _Lxx/_Exx GPE methods that have just been loaded.  in AcpiEvUpdateGpes()
374         /* Walk all Gpe Blocks attached to this interrupt level */  in AcpiEvUpdateGpes()
418  *              Extract the name and GPE type from the object, saving this
419  *              information for quick lookup during GPE dispatch. Allows a
423  *              The name of each GPE control method is of the form:
425  *                  L      - means that the GPE is level triggered
426  *                  E      - means that the GPE is edge triggered
427  *                  xx     - is the GPE number [in HEX]
429  * If WalkInfo->ExecuteByOwnerId is TRUE, we only execute examine GPE methods
463      * Match and decode the _Lxx and _Exx GPE method names  in AcpiEvMatchGpeMethod()
498             "Ignoring unknown GPE method type: %s "  in AcpiEvMatchGpeMethod()
503     /* 4) The last two characters of the name are the hex GPE Number */  in AcpiEvMatchGpeMethod()
511             "Could not extract GPE number from name: %s "  in AcpiEvMatchGpeMethod()
516     /* Ensure that we have a valid GPE number for this GPE block */  in AcpiEvMatchGpeMethod()
523          * This GpeNumber is not valid for this GPE block, just ignore it.  in AcpiEvMatchGpeMethod()
524          * However, it may be valid for a different GPE block, since GPE0  in AcpiEvMatchGpeMethod()
535         /* If there is already a handler, ignore this GPE method */  in AcpiEvMatchGpeMethod()
550                 "For GPE 0x%.2X, found both _L%2.2X and _E%2.2X methods",  in AcpiEvMatchGpeMethod()
556     /* Disable the GPE in case it's been enabled already. */  in AcpiEvMatchGpeMethod()
561      * Add the GPE information from above to the GpeEventInfo block for  in AcpiEvMatchGpeMethod()
562      * use during dispatch of this GPE.  in AcpiEvMatchGpeMethod()
570         "Registered GPE method %s as GPE number 0x%.2X\n",  in AcpiEvMatchGpeMethod()