xref: /linux/Documentation/ABI/testing/debugfs-ec (revision cd89e08fa020f5a882f922e3c9e2628235ca6715)
1*cd89e08fSThomas RenningerWhat:		/sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
2*cd89e08fSThomas RenningerDate:		July 2010
3*cd89e08fSThomas RenningerContact:	Thomas Renninger <trenn@suse.de>
4*cd89e08fSThomas RenningerDescription:
5*cd89e08fSThomas Renninger
6*cd89e08fSThomas RenningerGeneral information like which GPE is assigned to the EC and whether
7*cd89e08fSThomas Renningerthe global lock should get used.
8*cd89e08fSThomas RenningerKnowing the EC GPE one can watch the amount of HW events related to
9*cd89e08fSThomas Renningerthe EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
10*cd89e08fSThomas Renninger/sys/firmware/acpi/interrupts/gpeXY
11*cd89e08fSThomas Renninger
12*cd89e08fSThomas RenningerThe io file is binary and a userspace tool located here:
13*cd89e08fSThomas Renningerftp://ftp.suse.com/pub/people/trenn/sources/ec/
14*cd89e08fSThomas Renningershould get used to read out the 256 Embedded Controller registers
15*cd89e08fSThomas Renningeror writing to them.
16*cd89e08fSThomas Renninger
17*cd89e08fSThomas RenningerCAUTION: Do not write to the Embedded Controller if you don't know
18*cd89e08fSThomas Renningerwhat you are doing! Rebooting afterwards also is a good idea.
19*cd89e08fSThomas RenningerThis can influence the way your machine is cooled and fans may
20*cd89e08fSThomas Renningernot get switched on again after you did a wrong write.
21