mk-rootfs.sh

hc

2023-12-11 072de836f53be56a70cecf70b43ae43b7ce17376

 kernel/Documentation/trace/events-power.rst
..
..
@@ -75,16 +75,6 @@
75
75
 target/flags update.
76
76
 ::
77
77
 
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
-
88
78
   pm_qos_update_target               "action=%s prev_value=%d curr_value=%d"
89
79
   pm_qos_update_flags                "action=%s prev_value=0x%x curr_value=0x%x"
90
80
 
..
..
@@ -92,7 +82,7 @@
92
82
 The second parameter is the previous QoS value.
93
83
 The third parameter is the current QoS value to update.
94
84
 
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.
96
86
 ::
97
87
 
98
88
   dev_pm_qos_add_request             "device=%s type=%s new_value=%d"
..
..
@@ -103,3 +93,12 @@
103
93
 QoS requests.
104
94
 The second parameter gives the request type (e.g. "DEV_PM_QOS_RESUME_LATENCY").
105
95
 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.