class SetOperatingPointLimits
Defined at line 181 of file fidling/gen/sdk/fidl/fuchsia.hardware.cpu.ctrl/fuchsia.hardware.cpu.ctrl/cpp/fidl/fuchsia.hardware.cpu.ctrl/cpp/markers.h
Sets the operational boundaries (minimum and maximum operating points)
for the device, when supported.
Limits define the allowable performance range for the performance
domain. They are primarily used for:
* Thermal Mitigation: Progressively lowering the maximum operating point
(moving from 0 toward n-1) to reduce power dissipation.
* Performance Boosting: Raising the minimum operating point (moving
from n-1 toward 0) when automatic performance matching is insufficient
for the current workload.
Limits are useful on platforms where ether hardware or the kernel
automatically manages performance. By setting boundaries, userspace can
enforce power and performance policies while allowing the underlying
system to react to high-fidelity signals in real-time.
When limits are applied, the active operating point is clamped to the range:
`[max(minimum_opp, maximim_opp), maximum_opp]`.
Note that `maximim_opp` and `minimum_opp` reside in the P-state range [n-1, 0].
This logic ensures that the `minimum_opp` can be adjusted independently while
always respecting the ceiling imposed by the `maximim_opp`.
Set the operating point limits to (n-1, 0) to effectively remove the limits.
Returns ZX_OK on success.
Returns ZX_ERR_OUT_OF_RANGE if the minimum_opp or maximum_opp is outside
of the range [n-1, 0], where n is the number of operating points
returned by GetOperatingPointCount().
Returns ZX_ERR_NOT_SUPPORTED if the device does not support limits.
Public Members
static const bool kHasClientToServer
static const bool kHasClientToServerBody
static const bool kHasServerToClient
static const bool kHasServerToClientBody
static const bool kHasNonEmptyUserFacingResponse
static const bool kHasDomainError
static const bool kHasFrameworkError
static const uint64_t kOrdinal