| .. | .. |
|---|
| 6 | 6 | General information like which GPE is assigned to the EC and whether |
|---|
| 7 | 7 | the global lock should get used. |
|---|
| 8 | 8 | Knowing the EC GPE one can watch the amount of HW events related to |
|---|
| 9 | | -the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe): |
|---|
| 9 | +the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`): |
|---|
| 10 | 10 | /sys/firmware/acpi/interrupts/gpeXY |
|---|
| 11 | 11 | |
|---|
| 12 | 12 | The io file is binary and a userspace tool located here: |
|---|
| .. | .. |
|---|
| 14 | 14 | should get used to read out the 256 Embedded Controller registers |
|---|
| 15 | 15 | or writing to them. |
|---|
| 16 | 16 | |
|---|
| 17 | | -CAUTION: Do not write to the Embedded Controller if you don't know |
|---|
| 18 | | -what you are doing! Rebooting afterwards also is a good idea. |
|---|
| 19 | | -This can influence the way your machine is cooled and fans may |
|---|
| 20 | | -not get switched on again after you did a wrong write. |
|---|
| 17 | +CAUTION: |
|---|
| 18 | + Do not write to the Embedded Controller if you don't know |
|---|
| 19 | + what you are doing! Rebooting afterwards also is a good idea. |
|---|
| 20 | + This can influence the way your machine is cooled and fans may |
|---|
| 21 | + not get switched on again after you did a wrong write. |
|---|