Home
last modified time | relevance | path

Searched full:gpe (Results 1 – 25 of 150) sorted by relevance

123456

/kernel/linux/linux-4.19/drivers/acpi/acpica/
Devxfgpe.c29 * DESCRIPTION: Complete GPE initialization and enable all GPEs that have
37 * after the system _PRW methods have been run, but also after a GPE Block
38 * Device has been added or if any new GPE methods have been added via a
83 * PARAMETERS: gpe_device - Parent GPE Device. NULL for GPE0/GPE1 in ACPI_EXPORT_SYMBOL()
84 * gpe_number - GPE level within the GPE block in ACPI_EXPORT_SYMBOL()
88 * DESCRIPTION: Add a reference to a GPE. On the first reference, the GPE is in ACPI_EXPORT_SYMBOL()
103 * Ensure that we have a valid GPE number and that there is some way in ACPI_EXPORT_SYMBOL()
104 * of handling the GPE (handler or a GPE method). In other words, we in ACPI_EXPORT_SYMBOL()
105 * won't allow a valid GPE to be enabled if there is no way to handle it. in ACPI_EXPORT_SYMBOL()
137 * PARAMETERS: gpe_device - Parent GPE Device. NULL for GPE0/GPE1 in ACPI_EXPORT_SYMBOL()
[all …]
Devgpe.c27 * PARAMETERS: gpe_event_info - GPE to update
31 * DESCRIPTION: Updates GPE register enable mask based upon whether there are
32 * runtime references to this GPE
55 /* Set the mask bit only if there are references to this GPE */ in acpi_ev_update_gpe_enable_mask()
70 * PARAMETERS: gpe_event_info - GPE to enable
74 * DESCRIPTION: Enable a GPE.
84 /* Enable the requested GPE */ in acpi_ev_enable_gpe()
94 * PARAMETERS: gpe_event_info - GPE to be blocked/unblocked
95 * is_masked - Whether the GPE is masked or not
99 * DESCRIPTION: Unconditionally mask/unmask a GPE during runtime.
[all …]
Devgpeinit.c4 * Module Name: evgpeinit - System GPE initialization and update
21 * Originally (2000 - 2010), the GPE initialization code performed a walk of
43 * DESCRIPTION: Initialize the GPE data structures and the FADT GPE 0/1 blocks
64 * Initialize the GPE Block(s) defined in the FADT in acpi_ev_gpe_initialize()
66 * Why the GPE register block lengths are divided by 2: From the ACPI in acpi_ev_gpe_initialize()
80 * Determine the maximum GPE number for this machine. in acpi_ev_gpe_initialize()
91 /* GPE block 0 exists (has both length and address > 0) */ in acpi_ev_gpe_initialize()
97 /* Install GPE Block 0 */ in acpi_ev_gpe_initialize()
109 "Could not create GPE Block 0")); in acpi_ev_gpe_initialize()
116 /* GPE block 1 exists (has both length and address > 0) */ in acpi_ev_gpe_initialize()
[all …]
Dhwgpe.c4 * Module Name: hwgpe - Low level GPE enable/disable/clear functions
31 * PARAMETERS: gpe_event_info - Info block for the GPE
33 * RETURN: Register mask with a one in the GPE bit position
35 * DESCRIPTION: Compute the register mask for this GPE. One bit is set in the
36 * correct position for the input GPE.
52 * PARAMETERS: gpe_event_info - Info block for the GPE to be disabled
57 * DESCRIPTION: Enable or disable a single GPE in the parent enable register.
58 * The enable_mask field of the involved GPE register must be
73 /* Get the info block for the entire GPE register */ in acpi_hw_low_set_gpe()
80 /* Get current value of the enable register that contains this GPE */ in acpi_hw_low_set_gpe()
[all …]
Devgpeblk.c4 * Module Name: evgpeblk - GPE block creation and initialization.
30 * PARAMETERS: gpe_block - New GPE block
32 * GPE block
36 * DESCRIPTION: Install new GPE block with mutex support
89 * PARAMETERS: gpe_block - Existing GPE block
93 * DESCRIPTION: Remove a GPE block
157 * PARAMETERS: gpe_block - New GPE block
161 * DESCRIPTION: Create the register_info and event_info blocks for this GPE block
178 /* Allocate the GPE register information block */ in acpi_ev_create_gpe_info_blocks()
191 * Allocate the GPE event_info block. There are eight distinct GPEs in acpi_ev_create_gpe_info_blocks()
[all …]
Devgpeutil.c4 * Module Name: evgpeutil - GPE utilities
22 * PARAMETERS: gpe_walk_callback - Routine called for each GPE block
27 * DESCRIPTION: Walk the GPE lists.
47 /* Walk all Gpe Blocks attached to this interrupt level */ in acpi_ev_walk_gpe_list()
52 /* One callback per GPE block */ in acpi_ev_walk_gpe_list()
83 * DESCRIPTION: Matches the input GPE index (0-current_gpe_count) with a GPE
84 * block device. NULL if the GPE is one of the FADT-defined GPEs.
100 * The GPE index is within this block, get the node. Leave the node in acpi_ev_get_gpe_device()
118 * PARAMETERS: interrupt_number - Interrupt for a GPE block
123 * DESCRIPTION: Get or Create a GPE interrupt block. There is one interrupt
[all …]
Dacevents.h14 * Conditions to trigger post enabling GPE polling:
15 * It is not sufficient to trigger edge-triggered GPE with specific GPE
59 * evgpe - Low-level GPE support
92 * evgpeblk - Upper-level GPE block support
118 * evgpeinit - GPE initialization and update
130 * evgpeutil - GPE utilities
/kernel/linux/linux-5.10/drivers/acpi/acpica/
Devgpe.c27 * PARAMETERS: gpe_event_info - GPE to update
31 * DESCRIPTION: Updates GPE register enable mask based upon whether there are
32 * runtime references to this GPE
55 /* Set the mask bit only if there are references to this GPE */ in acpi_ev_update_gpe_enable_mask()
70 * PARAMETERS: gpe_event_info - GPE to enable
74 * DESCRIPTION: Enable a GPE.
84 /* Enable the requested GPE */ in acpi_ev_enable_gpe()
94 * PARAMETERS: gpe_event_info - GPE to be blocked/unblocked
95 * is_masked - Whether the GPE is masked or not
99 * DESCRIPTION: Unconditionally mask/unmask a GPE during runtime.
[all …]
Devxfgpe.c29 * DESCRIPTION: Complete GPE initialization and enable all GPEs that have
37 * after the system _PRW methods have been run, but also after a GPE Block
38 * Device has been added or if any new GPE methods have been added via a
83 * PARAMETERS: gpe_device - Parent GPE Device. NULL for GPE0/GPE1 in ACPI_EXPORT_SYMBOL()
84 * gpe_number - GPE level within the GPE block in ACPI_EXPORT_SYMBOL()
88 * DESCRIPTION: Add a reference to a GPE. On the first reference, the GPE is in ACPI_EXPORT_SYMBOL()
103 * Ensure that we have a valid GPE number and that there is some way in ACPI_EXPORT_SYMBOL()
104 * of handling the GPE (handler or a GPE method). In other words, we in ACPI_EXPORT_SYMBOL()
105 * won't allow a valid GPE to be enabled if there is no way to handle it. in ACPI_EXPORT_SYMBOL()
137 * PARAMETERS: gpe_device - Parent GPE Device. NULL for GPE0/GPE1 in ACPI_EXPORT_SYMBOL()
[all …]
Devgpeinit.c4 * 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()
[all …]
Dhwgpe.c4 * Module Name: hwgpe - Low level GPE enable/disable/clear functions
32 * reg - GPE register structure
36 * DESCRIPTION: Read from a GPE register in either memory or IO space.
73 * reg - GPE register structure
77 * DESCRIPTION: Write to a GPE register in either memory or IO space.
101 * PARAMETERS: gpe_event_info - Info block for the GPE
103 * RETURN: Register mask with a one in the GPE bit position
105 * DESCRIPTION: Compute the register mask for this GPE. One bit is set in the
106 * correct position for the input GPE.
122 * PARAMETERS: gpe_event_info - Info block for the GPE to be disabled
[all …]
Devgpeblk.c4 * Module Name: evgpeblk - GPE block creation and initialization.
30 * PARAMETERS: gpe_block - New GPE block
32 * GPE block
36 * DESCRIPTION: Install new GPE block with mutex support
89 * PARAMETERS: gpe_block - Existing GPE block
93 * DESCRIPTION: Remove a GPE block
160 * PARAMETERS: gpe_block - New GPE block
164 * DESCRIPTION: Create the register_info and event_info blocks for this GPE block
181 /* Allocate the GPE register information block */ in acpi_ev_create_gpe_info_blocks()
194 * Allocate the GPE event_info block. There are eight distinct GPEs in acpi_ev_create_gpe_info_blocks()
[all …]
Devgpeutil.c4 * Module Name: evgpeutil - GPE utilities
22 * PARAMETERS: gpe_walk_callback - Routine called for each GPE block
27 * DESCRIPTION: Walk the GPE lists.
47 /* Walk all Gpe Blocks attached to this interrupt level */ in acpi_ev_walk_gpe_list()
52 /* One callback per GPE block */ in acpi_ev_walk_gpe_list()
83 * DESCRIPTION: Matches the input GPE index (0-current_gpe_count) with a GPE
84 * block device. NULL if the GPE is one of the FADT-defined GPEs.
100 * The GPE index is within this block, get the node. Leave the node in acpi_ev_get_gpe_device()
118 * PARAMETERS: interrupt_number - Interrupt for a GPE block
123 * DESCRIPTION: Get or Create a GPE interrupt block. There is one interrupt
[all …]
Dacevents.h14 * Conditions to trigger post enabling GPE polling:
15 * It is not sufficient to trigger edge-triggered GPE with specific GPE
59 * evgpe - Low-level GPE support
92 * evgpeblk - Upper-level GPE block support
118 * evgpeinit - GPE initialization and update
130 * evgpeutil - GPE utilities
/kernel/linux/linux-4.19/arch/arm/boot/dts/
Ds3c2416-pinctrl.dtsi35 gpe: gpe { label
124 samsung,pins = "gpe-14", "gpe-15";
129 samsung,pins = "gpe-11", "gpe-12", "gpe-13";
134 samsung,pins = "gpe-5";
139 samsung,pins = "gpe-6";
144 samsung,pins = "gpe-7";
149 samsung,pins = "gpe-8", "gpe-9", "gpe-10";
Ds3c64xx-pinctrl.dtsi47 gpe: gpe { label
341 samsung,pins = "gpe-0", "gpe-2", "gpe-3", "gpe-4";
347 samsung,pins = "gpe-1";
380 samsung,pins = "gpe-0", "gpe-2", "gpe-3", "gpe-4";
386 samsung,pins = "gpe-1";
398 samsung,pins = "gpe-0", "gpe-1", "gpe-2", "gpe-3", "gpe-4";
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Ds3c2416-pinctrl.dtsi35 gpe: gpe { label
124 samsung,pins = "gpe-14", "gpe-15";
129 samsung,pins = "gpe-11", "gpe-12", "gpe-13";
134 samsung,pins = "gpe-5";
139 samsung,pins = "gpe-6";
144 samsung,pins = "gpe-7";
149 samsung,pins = "gpe-8", "gpe-9", "gpe-10";
Ds3c64xx-pinctrl.dtsi47 gpe: gpe { label
341 samsung,pins = "gpe-0", "gpe-2", "gpe-3", "gpe-4";
347 samsung,pins = "gpe-1";
380 samsung,pins = "gpe-0", "gpe-2", "gpe-3", "gpe-4";
386 samsung,pins = "gpe-1";
398 samsung,pins = "gpe-0", "gpe-1", "gpe-2", "gpe-3", "gpe-4";
/kernel/linux/linux-5.10/drivers/acpi/
Dec.c129 * this threshold, will think there is a GPE storm happened and
130 * will disable the GPE for normal transaction.
134 MODULE_PARM_DESC(ec_storm_threshold, "Maxim false GPE numbers not considered as GPE storm");
185 static int EC_FLAGS_IGNORE_DSDT_GPE; /* Needs ECDT GPE as correction setting */
186 static int EC_FLAGS_TRUST_DSDT_GPE; /* Needs DSDT GPE as correction setting */
336 * GPE Registers
343 (void)acpi_get_gpe_status(NULL, ec->gpe, &gpe_status); in acpi_ec_is_gpe_raised()
350 acpi_enable_gpe(NULL, ec->gpe); in acpi_ec_enable_gpe()
353 acpi_set_gpe(NULL, ec->gpe, ACPI_GPE_ENABLE); in acpi_ec_enable_gpe()
357 * On some platforms, EN=1 writes cannot trigger GPE. So in acpi_ec_enable_gpe()
[all …]
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Ddebugfs-ec1 What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
6 General information like which GPE is assigned to the EC and whether
8 Knowing the EC GPE one can watch the amount of HW events related to
9 the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
Dsysfs-firmware-acpi60 number of a "General Purpose Events" (GPE).
62 A GPE vectors to a specified handler in AML, which
64 OS context. GPE 0x12, for example, would vector
128 gpeXX - count for individual GPE source
142 invalid: it's either a GPE or a Fixed Event that
145 disable: the GPE/Fixed Event is valid but disabled.
147 enable: the GPE/Fixed Event is valid and enabled.
162 Note that only writing to VALID GPE/Fixed Event is allowed,
163 i.e. user can only change the status of runtime GPE and
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Ddebugfs-ec1 What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
6 General information like which GPE is assigned to the EC and whether
8 Knowing the EC GPE one can watch the amount of HW events related to
9 the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
Dsysfs-firmware-acpi65 number of a "General Purpose Events" (GPE).
67 A GPE vectors to a specified handler in AML, which
69 OS context. GPE 0x12, for example, would vector
134 gpeXX count for individual GPE source
148 invalid it's either a GPE or a Fixed Event that
151 disable the GPE/Fixed Event is valid but disabled.
153 enable the GPE/Fixed Event is valid and enabled.
171 Note that only writing to VALID GPE/Fixed Event is allowed,
172 i.e. user can only change the status of runtime GPE and
/kernel/linux/linux-4.19/drivers/acpi/
Dec.c110 EC_FLAGS_GPE_HANDLER_INSTALLED, /* GPE handler installed */
115 EC_FLAGS_GPE_MASKED, /* GPE masked */
142 * this threshold, will think there is a GPE storm happened and
143 * will disable the GPE for normal transaction.
147 MODULE_PARM_DESC(ec_storm_threshold, "Maxim false GPE numbers not considered as GPE storm");
196 static int EC_FLAGS_IGNORE_DSDT_GPE; /* Needs ECDT GPE as correction setting */
346 * GPE Registers
353 (void)acpi_get_gpe_status(NULL, ec->gpe, &gpe_status); in acpi_ec_is_gpe_raised()
360 acpi_enable_gpe(NULL, ec->gpe); in acpi_ec_enable_gpe()
363 acpi_set_gpe(NULL, ec->gpe, ACPI_GPE_ENABLE); in acpi_ec_enable_gpe()
[all …]
/kernel/linux/linux-5.10/arch/mips/boot/dts/ingenic/
Dgcw0.dts44 gpio = <&gpe 9 0>;
143 gpios = <&gpe 21 GPIO_ACTIVE_LOW>;
150 gpios = <&gpe 25 GPIO_ACTIVE_LOW>;
157 gpios = <&gpe 23 GPIO_ACTIVE_LOW>;
164 gpios = <&gpe 24 GPIO_ACTIVE_LOW>;
171 gpios = <&gpe 29 GPIO_ACTIVE_LOW>;
178 gpios = <&gpe 20 GPIO_ACTIVE_LOW>;
185 gpios = <&gpe 27 GPIO_ACTIVE_LOW>;
192 gpios = <&gpe 28 GPIO_ACTIVE_LOW>;
206 gpios = <&gpe 26 GPIO_ACTIVE_LOW>;
[all …]

123456