Priyanka Mathur | 26b4a4b | 2012-11-05 13:45:45 -0800 | [diff] [blame] | 1 | Subsystem Trace Points: msm_low_power |
| 2 | |
| 3 | The msm_low_power tracing system captures the events during the entry |
| 4 | and exit of various low power modes like power collapse, standalone |
| 5 | power collapse, retention and wfi. The tracing system adds the following |
| 6 | events to capture the state of the low power mode. |
| 7 | |
| 8 | 1) msm_pm_enter |
| 9 | =================== |
| 10 | msm_pm_enter: cpu: %u latency: %uus sleep: %uus |
| 11 | msm_pm_enter_pc: cpu: %u latency: %uus sleep: %uus wake_up: %u |
| 12 | msm_pm_enter_ret: cpu: %u latency: %uus sleep: %uus wake_up: %u |
| 13 | msm_pm_enter_spc: cpu: %u latency: %uus sleep: %uus wake_up: %u |
| 14 | msm_pm_enter_wfi: cpu: %u latency: %uus sleep: %uus wake_up: %u |
| 15 | |
| 16 | The event captures various parameters during the entry into low power |
| 17 | modes. |
| 18 | |
| 19 | The 'cpu' parameter represents the cpu on which the low power mode is |
| 20 | chosen. |
| 21 | |
| 22 | The 'latency_us' parameter represents the system latency at the time of |
| 23 | choosing the low power mode. |
| 24 | |
| 25 | The 'sleep_us' parameter tells the maximum amount of time the kernel can |
| 26 | sleep in this low power mode. |
| 27 | |
| 28 | The 'wake_up' parameter tells if there was any immediate wakeup required |
| 29 | before entering low power mode. |
| 30 | |
| 31 | 2) msm_pm_exit |
| 32 | ================= |
| 33 | msm_pm_exit: cpu:%u success:%d |
| 34 | msm_pm_exit_pc: cpu:%u success:%d |
| 35 | msm_pm_exit_ret: cpu:%u success:%d |
| 36 | msm_pm_exit_spc: cpu:%u success:%d |
| 37 | msm_pm_exit_wfi: cpu:%u success:%d |
| 38 | |
| 39 | The event captures parameters during the exit of the low power modes. |
| 40 | |
| 41 | The 'cpu' parameter represents the cpu on which the low power mode is chosen. |
| 42 | |
| 43 | The 'success' parameter shows the state of power collapse/standalone power |
| 44 | collapse. It will be set if power collapse/standalone power collapse were |
| 45 | successful. For the rest of the low power modes it is set to one. |
Priyanka Mathur | b44bf57 | 2012-11-07 12:07:45 -0800 | [diff] [blame] | 46 | |
| 47 | 3) lpm_resources |
| 48 | ================= |
| 49 | lpm_resources: name:%s sleep_value:%d |
| 50 | |
| 51 | This event captures parameters for each of the lpm resources. |
| 52 | |
| 53 | The 'name' parameter represents the name of the lpm resource and it can hold |
| 54 | l2, pxo, vdd mem, vdd dig depending on the resource chosen during power |
| 55 | collapse. |
| 56 | |
| 57 | The 'sleep_value' parameter corresponds to the sleep value set for the resource. |