>> After 6217 is applied, when installing EC GPE handler, Linux will invoke >> acpi_hw_write_gpe_enable_reg to try to disable EC GPE which is not done >> before. Don't know if this is related. >No, EC GPE handler is installed later. Thus the error is triggered >during execution of 6217 code... Attempt to disable EC GPE causes a GPE? I still do not understand. >-----Original Message----- >From: Alexey Starikovskiy [mailto:astarikovskiy@xxxxxxx] >Sent: Thursday, April 24, 2008 7:40 PM >To: Zhang, Rui >Cc: Moore, Robert; Len Brown; linux-acpi@xxxxxxxxxxxxxxx >Subject: Re: [PATCH 70/73] ACPICA: Fix to disable unknown spurious GPEs > >Zhang Rui wrote: >> On Fri, 2008-04-25 at 10:10 +0800, Alexey Starikovskiy wrote: >>> Actually, I too don't know why _disabling_ some GPE could trigger EC >>> one... >>> May be Len could try to debug this issue, as he is the only one with >>> hardware... >>> One thought is that EC GPE is not present in GPE scope, thus it will >>> be not configured by the >>> time 6217' code is executed. So, in theory, 6217 could try to disable >>> EC GPE. >> In acpi_install_gpe_handler, Linux always disables the GPE before >> installing a GPE handler. >> After 6217 is applied, when installing EC GPE handler, Linux will invoke >> acpi_hw_write_gpe_enable_reg to try to disable EC GPE which is not done >> before. Don't know if this is related. >No, EC GPE handler is installed later. Thus the error is triggered >during execution of 6217 code... -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
