>-----Original Message----- >From: Len Brown [mailto:lenb@xxxxxxxxxx] >Sent: Friday, June 20, 2008 2:54 PM >To: Zhang, Rui >Cc: linux-acpi; Lin, Ming M; Alexey Starikovskiy >Subject: Re: [RFC PATCH 1/2] ACPI: allow enable/disable/clear ACPI interrupts >in user space > >> >> applied to acpi-test > >rats, i lied. >this conflicts with the acpica branch in acpi-test, >and I'm too lazy to deal with the conflict at this hour. > >I expect the acpica branch to go upstream in 2.6.27, and I'd like to see >this feature too. Any chance you can re-base this patch on top of the >current linux-acpi test tree? Sure, I'll re-send it out sometime tomorrow. :) Thanks, rui > >> On Fri, 20 Jun 2008, Zhang Rui wrote: >> >> > From: Zhang Rui <rui.zhang@xxxxxxxxx> >> > >> > Allow users to enable/disable/clear a specific & valid GPE/Fixed Event in >user space. >> > >> > Note: This is useful for debugging, especially for some interrupt storm >issues. >> > >> > Note: All wakeup GPEs are disabled and they can not be enabled at runtime, >and we mark them as invalid. >> > All GPEs that don't have a _Lxx/_Exx method are marked as invalid. >> > All Fixed Events that don't have an event handler are marked as invalid >and they can't be enabled >> > until an event handler is registered. >> > >> > Signed-off-by: Zhang Rui <rui.zhang@xxxxxxxxx> >> > Signed-off-by: Ling Ming <ming.m.lin@xxxxxxxxx> >> > --- >> > Documentation/ABI/testing/sysfs-firmware-acpi | 127 >+++++++++++++------ >> > drivers/acpi/events/evxfevnt.c | 18 ++ >> > drivers/acpi/hardware/hwgpe.c | 2 >> > drivers/acpi/system.c | 169 >++++++++++++++++++++++++-- >> > include/acpi/achware.h | 2 >> > include/acpi/acpixf.h | 4 >> > 6 files changed, 258 insertions(+), 64 deletions(-) >> > >> -- >> 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 >> -- 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
