• Alex Shi's avatar
    CPU / PM: expose pm_qos_resume_latency for CPUs · 37efa4b4
    Alex Shi authored
    The cpu-dma PM QoS constraint impacts all the cpus in the system. There
    is no way to let the user to choose a PM QoS constraint per cpu.
    
    The following patch exposes to the userspace a per cpu based sysfs file
    in order to let the userspace to change the value of the PM QoS latency
    constraint.
    
    This change is inoperative in its form and the cpuidle governors have to
    take into account the per cpu latency constraint in addition to the
    global cpu-dma latency constraint in order to operate properly.
    
    BTW
    The pm_qos_resume_latency usage defined in
    Documentation/ABI/testing/sysfs-devices-power
    The /sys/devices/.../power/pm_qos_resume_latency_us attribute
    contains the PM QoS resume latency limit for the given device,
    which is the maximum allowed time it can take to resume the
    device, after it has been suspended at run time, from a resume
    request to the moment the device will be ready to process I/O,
    in microseconds.  If it is equal to 0, however, this means that
    the PM QoS resume latency may be arbitrary.
    Signed-off-by: default avatarAlex Shi <alex.shi@linaro.org>
    Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    37efa4b4
cpu.c 11.9 KB