hc
2023-12-11 d2ccde1c8e90d38cee87a1b0309ad2827f3fd30d
kernel/Documentation/trace/events-power.rst
....@@ -75,16 +75,6 @@
7575 target/flags update.
7676 ::
7777
78
- pm_qos_add_request "pm_qos_class=%s value=%d"
79
- pm_qos_update_request "pm_qos_class=%s value=%d"
80
- pm_qos_remove_request "pm_qos_class=%s value=%d"
81
- pm_qos_update_request_timeout "pm_qos_class=%s value=%d, timeout_us=%ld"
82
-
83
-The first parameter gives the QoS class name (e.g. "CPU_DMA_LATENCY").
84
-The second parameter is value to be added/updated/removed.
85
-The third parameter is timeout value in usec.
86
-::
87
-
8878 pm_qos_update_target "action=%s prev_value=%d curr_value=%d"
8979 pm_qos_update_flags "action=%s prev_value=0x%x curr_value=0x%x"
9080
....@@ -92,7 +82,7 @@
9282 The second parameter is the previous QoS value.
9383 The third parameter is the current QoS value to update.
9484
95
-And, there are also events used for device PM QoS add/update/remove request.
85
+There are also events used for device PM QoS add/update/remove request.
9686 ::
9787
9888 dev_pm_qos_add_request "device=%s type=%s new_value=%d"
....@@ -103,3 +93,12 @@
10393 QoS requests.
10494 The second parameter gives the request type (e.g. "DEV_PM_QOS_RESUME_LATENCY").
10595 The third parameter is value to be added/updated/removed.
96
+
97
+And, there are events used for CPU latency QoS add/update/remove request.
98
+::
99
+
100
+ pm_qos_add_request "value=%d"
101
+ pm_qos_update_request "value=%d"
102
+ pm_qos_remove_request "value=%d"
103
+
104
+The parameter is the value to be added/updated/removed.