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