18c2ecf20Sopenharmony_ciWhat:		/sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
28c2ecf20Sopenharmony_ciDate:		July 2010
38c2ecf20Sopenharmony_ciContact:	Thomas Renninger <trenn@suse.de>
48c2ecf20Sopenharmony_ciDescription:
58c2ecf20Sopenharmony_ci
68c2ecf20Sopenharmony_ciGeneral information like which GPE is assigned to the EC and whether
78c2ecf20Sopenharmony_cithe global lock should get used.
88c2ecf20Sopenharmony_ciKnowing the EC GPE one can watch the amount of HW events related to
98c2ecf20Sopenharmony_cithe EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
108c2ecf20Sopenharmony_ci/sys/firmware/acpi/interrupts/gpeXY
118c2ecf20Sopenharmony_ci
128c2ecf20Sopenharmony_ciThe io file is binary and a userspace tool located here:
138c2ecf20Sopenharmony_ciftp://ftp.suse.com/pub/people/trenn/sources/ec/
148c2ecf20Sopenharmony_cishould get used to read out the 256 Embedded Controller registers
158c2ecf20Sopenharmony_cior writing to them.
168c2ecf20Sopenharmony_ci
178c2ecf20Sopenharmony_ciCAUTION:
188c2ecf20Sopenharmony_ci  Do not write to the Embedded Controller if you don't know
198c2ecf20Sopenharmony_ci  what you are doing! Rebooting afterwards also is a good idea.
208c2ecf20Sopenharmony_ci  This can influence the way your machine is cooled and fans may
218c2ecf20Sopenharmony_ci  not get switched on again after you did a wrong write.
22