PM / QoS: Introduce latency tolerance device PM QoS type
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest6 patches 0 repliesNew
- v26 patches 2 repliesSuperseded
- v15 patches 3 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | PM / QoS: Rename device resume latency QoS itemsDocumentation/ Documentation/ drivers/ +5 more | +73 | 0 replies | |
| 2/6 | PM / QoS: Add no_constraints_value field to struct pm_qos_constraintsdrivers/ include/ kernel/ | +6 | 0 replies | |
| 3/6 | PM / QoS: Introcuce latency tolerance device PM QoS typeDocumentation/ Documentation/ drivers/ +4 more | +278 | 0 replies | |
| 4/6 | ACPI / scan: Add bind/unbind callbacks to struct acpi_scan_handlerdrivers/ drivers/ include/ | +19 | 0 replies | |
| 5/6 | ACPI / LPSS: Support for device latency tolerance PM QoSdrivers/ | +70 | 0 replies | |
| 5/6 | ACPI / LPSS: Support for device latency tolerance PM QoSdrivers/ | +70 | 0 replies | |
| 6/6 | PM / QoS: Add type to dev_pm_qos_add_ancestor_request() argumentsDocumentation/ drivers/ drivers/ +1 more | +28 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/6] PM / QoS: Introduce latency tolerance device PM QoS type
Quoted 29 lines · Rafael J. Wysocki
Quoted 28 lines · Rafael J. Wysocki
Hi All,
On some platforms hardware may switch to an energy-saving mode on the fly on the basis of certain utilization metrics used by it. That usually is desirable from the energy conservation standpoint, but it generally causes latencies to increase which may adversely affect some operations. For this reason, the platforms in question usually provide some interfaces for software to indicate its latency tolerance and possibly to prevent the energy-saving modes from being selected too aggressively.
The following series of patches introduces a device PM QoS type allowing those interfaces to be used by kernel code and user space. It is designed in analogy with the existing resume latency device PM QoS type, which allows some pieces of the existing device PM QoS code to be re-used and makes the new user space interface fit into the existing framework.
Patch [1/5] modifies the names of symbols, variables, functions and structure fields associated with the existing resume latency device PM QoS type to avoid any confusion with the new one introduced by the subsequent patches.
Patch [2/5] introduces a new field in struct
pm_qos_constraintsfor specifying a special value to be returned as the effective requirement when the given list of PM QoS requirements is empty. That field is necessary for the new latency tolerance device PM QoS type.Patch [3/5] introduces the latency tolerance device PM QoS type along with documentation.
Quoted 8 lines
Quoted 6 lines
Patch [4/5] modifies the ACPI LPSS (Low-Power Subsystem) driver to hook up LPSS devices to the new latency tolerance device PM QoS interface.
Patch [5/5] modifies the
dev_pm_qos_add_ancestor_request()routine so that it can be used by drivers of devices without hardware latency tolerance support for specifying their requirements via the ancestors of those devies.As usual, testing uncovered some issues, so an updated series follows.
OK, no comments - no objections. Cool! :-)
Time for a non-RFC submission I guess.
The following series is almost the same as the previous one except for patch [5/6] that fixes a bug (LPSS_LTR_SNOOP_REQ has to be set along with LPSS_LTR_SNOOP_LAT_1US) and introduces a cutoff value such that all above it will mean "no requirement".
Thanks!
Signature · 2 lines
I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.