Lines Matching +full:per +full:- +full:device

11  * The per-device PM QoS framework provides the API to manage the
12    per-device latency constraints and PM QoS flags.
65 The infrastructure exposes one device node, /dev/cpu_dma_latency, for the CPU
75 As long as the device node is held open that process has a registered
79 the open device node.  Alternatively, it can write a hex string for the value
83 To remove the user mode request for a target value simply close the device
87 2. PM QoS per-device latency and flags framework
90 For each device, there are three lists of PM QoS requests. Two of them are
98 values.  One device PM QoS flag is defined currently: PM_QOS_FLAG_NO_POWER_OFF.
106 int dev_pm_qos_add_request(device, handle, type, value):
107   Will insert an element into the list for that identified device with the
123 s32 dev_pm_qos_read_value(device, type):
124   Returns the aggregated value for a given device's constraints list.
126 enum pm_qos_flags_status dev_pm_qos_flags(device, mask)
127   Check PM QoS flags of the given device against the given mask of flags.
137 		The device's PM QoS structure has not been initialized
141   Add a PM QoS request for the first direct ancestor of the given device whose
146 int dev_pm_qos_expose_latency_limit(device, value)
147   Add a request to the device's PM QoS list of resume latency constraints and
148   create a sysfs attribute pm_qos_resume_latency_us under the device's power
151 void dev_pm_qos_hide_latency_limit(device)
152   Drop the request added by dev_pm_qos_expose_latency_limit() from the device's
154   pm_qos_resume_latency_us from the device's power directory.
156 int dev_pm_qos_expose_flags(device, value)
157   Add a request to the device's PM QoS list of flags and create sysfs attribute
158   pm_qos_no_power_off under the device's power directory allowing user space to
161 void dev_pm_qos_hide_flags(device)
162   Drop the request added by dev_pm_qos_expose_flags() from the device's PM QoS
163   list of flags and remove sysfs attribute pm_qos_no_power_off from the device's
168 The per-device PM QoS framework has a per-device notification tree.
170 int dev_pm_qos_add_notifier(device, notifier, type):
171   Adds a notification callback function for the device for a particular request
174   The callback is called when the aggregated value of the device constraints
177 int dev_pm_qos_remove_notifier(device, notifier, type):
178   Removes the notification callback function for the device.
184 This device PM QoS type is used to support systems in which hardware may switch
185 to energy-saving operation modes on the fly.  In those systems, if the operation
190 If there is a latency tolerance control mechanism for a given device available
191 to software, the .set_latency_tolerance callback in that device's dev_pm_info
196 Whenever the effective latency tolerance changes for the device, its
199 latency tolerance requirements for the device is empty, the callback is expected
204 automatically updating the device's latency tolerance in response to its power
208 If .set_latency_tolerance() is present for the device, sysfs attribute
211 requirement for the device, if any.  Writing "any" to it means "no requirement,
214 requirements from the kernel side in the device's list.
217 DEV_PM_QOS_LATENCY_TOLERANCE device PM QoS type to add, remove and update