diff options
author | Ben Widawsky <ben@bwidawsk.net> | 2012-09-12 18:12:07 -0700 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-09-20 14:23:06 +0200 |
commit | 46ddf194776500e132693dd2c11b28a971070cc0 (patch) | |
tree | c216e4694d15393519ca5e39bca026b81563a5dc /lib/lru_cache.c | |
parent | b6f69c9a7f800c9f22cc94aa193f8451b3cc299c (diff) | |
download | talos-obmc-linux-46ddf194776500e132693dd2c11b28a971070cc0.tar.gz talos-obmc-linux-46ddf194776500e132693dd2c11b28a971070cc0.zip |
drm/i915: Add setters for min/max frequency
Provide a standardized sysfs interface for setting min, and max
frequencies. The code which reads the limits were lifted from the
debugfs files. As a brief explanation, the limits are similar to the CPU
p-states. We have 3 states:
RP0 - ie. max frequency
RP1 - ie. "preferred min" frequency
RPn - seriously lowest frequency
Initially Daniel asked me to clamp the writes to supported values, but
in conforming to the way the cpufreq drivers seem to work, instead
return -EINVAL (noticed by Jesse in discussion).
The values can be used by userspace wishing to control the limits of the
GPU (see the CC list for people who care).
v4: Make exceeding the soft limits return -EINVAL as well (Daniel)
v3: bug fix (Ben) - was passing the MHz value to gen6_set_rps instead of
the step value. To fix, deal only with step values by doing the divide
at the top.
v2: add the dropped mutex_unlock in error cases (Chris)
EINVAL on both too min, or too max (Daniel)
v2 Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
CC: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'lib/lru_cache.c')
0 files changed, 0 insertions, 0 deletions