cd89e08fa0
Signed-off-by: Thomas Renninger <trenn@suse.de> CC: Alexey Starikovskiy <astarikovskiy@suse.de> CC: Len Brown <lenb@kernel.org> CC: linux-kernel@vger.kernel.org CC: linux-acpi@vger.kernel.org CC: platform-driver-x86@vger.kernel.org Signed-off-by: Matthew Garrett <mjg@redhat.com>
20 lines
838 B
Text
20 lines
838 B
Text
What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
|
|
Date: July 2010
|
|
Contact: Thomas Renninger <trenn@suse.de>
|
|
Description:
|
|
|
|
General information like which GPE is assigned to the EC and whether
|
|
the global lock should get used.
|
|
Knowing the EC GPE one can watch the amount of HW events related to
|
|
the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
|
|
/sys/firmware/acpi/interrupts/gpeXY
|
|
|
|
The io file is binary and a userspace tool located here:
|
|
ftp://ftp.suse.com/pub/people/trenn/sources/ec/
|
|
should get used to read out the 256 Embedded Controller registers
|
|
or writing to them.
|
|
|
|
CAUTION: Do not write to the Embedded Controller if you don't know
|
|
what you are doing! Rebooting afterwards also is a good idea.
|
|
This can influence the way your machine is cooled and fans may
|
|
not get switched on again after you did a wrong write.
|