Lines Matching full:constraint

402 [If there is a wakeup latency constraint coming from the `PM QoS framework
405 latency within the constraint is preselected without consulting the ``hits``,
588 global constraint in the ``PM_QOS_CPU_DMA_LATENCY`` class and through the
594 resume latency constraint for a CPU can be modified by user space by writing a
600 number will be interpreted as a requested PM QoS constraint in microseconds.
602 The requested value is not automatically applied as a new constraint, however,
604 constraint previously requested by someone else.  For this reason, the PM QoS
607 (minimum in this particular case) value as the new constraint.
614 request represented by it as a new requested constraint value.  Next, the
617 constraint.  Thus setting a new requested constraint value will only change the
618 real constraint if the effective "list" value is affected by it.  In particular,
619 for the ``PM_QOS_CPU_DMA_LATENCY`` class it only affects the real constraint if
630 and that value will become the new real constraint.
640 ``sysfs`` interface to control the resume latency constraint for it.]  It
642 determine the effective value to be set as the resume latency constraint for the
647 effective ``PM_QOS_CPU_DMA_LATENCY`` class constraint and the effective
648 resume latency constraint for the given CPU as the upper limit for the exit