4  * Module Name: evgpeinit - System GPE initialization and update
21  * Originally (2000 - 2010), the GPE initialization code performed a walk of
53  * DESCRIPTION: Initialize the GPE data structures and the FADT GPE 0/1 blocks
75 	 * Initialize the GPE Block(s) defined in the FADT  in acpi_ev_gpe_initialize()
77 	 * Why the GPE register block lengths are divided by 2:  From the ACPI  in acpi_ev_gpe_initialize()
91 	 * Determine the maximum GPE number for this machine.  in acpi_ev_gpe_initialize()
103 		/* GPE block 0 exists (has both length and address > 0) */  in acpi_ev_gpe_initialize()
109 		/* Install GPE Block 0 */  in acpi_ev_gpe_initialize()
120 					"Could not create GPE Block 0"));  in acpi_ev_gpe_initialize()
128 		/* GPE block 1 exists (has both length and address > 0) */  in acpi_ev_gpe_initialize()
137 				    "GPE0 block (GPE 0 to %u) overlaps the GPE1 block "  in acpi_ev_gpe_initialize()
138 				    "(GPE %u to %u) - Ignoring GPE1",  in acpi_ev_gpe_initialize()
148 			/* Install GPE Block 1 */  in acpi_ev_gpe_initialize()
163 						"Could not create GPE Block 1"));  in acpi_ev_gpe_initialize()
167 			 * GPE0 and GPE1 do not have to be contiguous in the GPE number  in acpi_ev_gpe_initialize()
168 			 * space. However, GPE0 always starts at GPE number zero.  in acpi_ev_gpe_initialize()
173 	/* Exit if there are no GPE registers */  in acpi_ev_gpe_initialize()
180 				  "There are no GPE blocks defined in the FADT\n"));  in acpi_ev_gpe_initialize()
197  * DESCRIPTION: Check for new GPE methods (_Lxx/_Exx) made available as a
198  *              result of a Load() or load_table() operation. If new GPE
211 	 * Find any _Lxx/_Exx GPE methods that have just been loaded.  in acpi_ev_update_gpes()
233 		/* Walk all Gpe Blocks attached to this interrupt level */  in acpi_ev_update_gpes()
275  *              Extract the name and GPE type from the object, saving this
276  *              information for quick lookup during GPE dispatch. Allows a
280  *              The name of each GPE control method is of the form:
282  *                  L      - means that the GPE is level triggered
283  *                  E      - means that the GPE is edge triggered
284  *                  xx     - is the GPE number [in HEX]
286  * If walk_info->execute_by_owner_id is TRUE, we only execute examine GPE methods
316 	 * Match and decode the _Lxx and _Exx GPE method names  in acpi_ev_match_gpe_method()
349 				  "Ignoring unknown GPE method type: %s "  in acpi_ev_match_gpe_method()
354 	/* 4) The last two characters of the name are the hex GPE Number */  in acpi_ev_match_gpe_method()
362 				  "Could not extract GPE number from name: %s "  in acpi_ev_match_gpe_method()
367 	/* Ensure that we have a valid GPE number for this GPE block */  in acpi_ev_match_gpe_method()
374 		 * This gpe_number is not valid for this GPE block, just ignore it.  in acpi_ev_match_gpe_method()
375 		 * However, it may be valid for a different GPE block, since GPE0  in acpi_ev_match_gpe_method()
386 		/* If there is already a handler, ignore this GPE method */  in acpi_ev_match_gpe_method()
399 				    "For GPE 0x%.2X, found both _L%2.2X and _E%2.2X methods",  in acpi_ev_match_gpe_method()
405 	/* Disable the GPE in case it's been enabled already. */  in acpi_ev_match_gpe_method()
410 	 * Add the GPE information from above to the gpe_event_info block for  in acpi_ev_match_gpe_method()
411 	 * use during dispatch of this GPE.  in acpi_ev_match_gpe_method()
418 			  "Registered GPE method %s as GPE number 0x%.2X\n",  in acpi_ev_match_gpe_method()