mark gross <markgross@xxxxxxxxxxx> writes: > just a quick note: ever since I lost my mgross@xxxxxxxxxxxxxxx email > I've started using markgross@xxxxxxxxxxx Sorry - I picked the @linux.intel.com address from git blame. Hmm.. is the mark.gross@xxxxxxxxx in MAINTAINERS still valid? > FWIW if this works the way I hope it does then, its a feature we need > for different reasons than interactivity. So thanks for working on > this! Thanks - I appreciate the feedback! >> V2: >> * split min and max to separate commits >> * handle PM QoS min above max as max >> * handle PM QoS max below min as min > > A qos to constrain how slow the cpu goes is ok. > A qos to constrain how fast it is allowed to go is not a PM_QOS thing. Thanks - I appreciate the feedback :-) As I said earlier, I think the maximum frequency can act as a level of energy efficiency request. If a workload knows that a certain level of performance is adequate, the maximum frequency request can prevent e.g. ondemand unnecessarily raising the frequency. --Antti -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
