1 What: /sys/kernel/debug/<cros-ec-device>/console_log
5 If the EC supports the CONSOLE_READ command type, this file
6 can be used to grab the EC logs. The kernel polls for the log
7 and keeps its own buffer but userspace should grab this and
8 write it out to some logs.
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
14 This file dumps the EC panic information from the previous
15 reboot. This file will only exist if the PANIC_INFO command
16 type is supported by the EC.
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
22 This file provides the port role, muxes and power debug
23 information for all the USB PD/type-C ports available. If
24 the are no ports available, this file will be just an empty
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
31 A u32 providing the time since EC booted in ms. This is
32 is used for synchronizing the AP host time with the EC
33 log. An error is returned if the command is not supported
34 by the EC or there is a communication problem.
36 What: /sys/kernel/debug/<cros-ec-device>/last_resume_result
40 Some ECs have a feature where they will track transitions to
41 the (Intel) processor's SLP_S0 line, in order to detect cases
42 where a system failed to go into S0ix. When the system resumes,
43 an EC with this feature will return a summary of SLP_S0
44 transitions that occurred. The last_resume_result file returns
45 the most recent response from the AP's resume message to the EC.
47 The bottom 31 bits contain a count of the number of SLP_S0
48 transitions that occurred since the suspend message was
49 received. Bit 31 is set if the EC attempted to wake the
50 system due to a timeout when watching for SLP_S0 transitions.
51 Callers can use this to detect a wake from the EC due to
52 S0ix timeouts. The result will be zero if no suspend
53 transitions have been attempted, or the EC does not support
56 Output will be in the format: "0x%08x\n".