Re: [PATCH 1/3] PM / QoS: Make it possible to expose PM QoS latency constraints

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday, March 09, 2012, Kevin Hilman wrote:
> Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> writes:
> 
> [...]
> 
> > How about calling it "runtime latency"?  Or "runtime wakeup latency" in 
> > case people think there might be some other sort of latency associated 
> > with runtime power management.
> 
> Either is better than just latency, but I would vote for runtime wakeup
> latency.

Well, that would be pm_qos_runtime_wakeup_latency_us.  Kind of long, IMHO.
Apart from this "wakeup" may be thought to refer to "remote wakeup", which
is when a device is resumed as a result of an external signal.

pm_qos_resume_latency_us is shorter and since it is referred to in the
documentation as "resume latency", I don't see any problems with that name.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux