diff options
| author | Sai Gurrappadi <sgurrappadi@nvidia.com> | 2017-08-09 13:35:44 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2017-08-11 18:46:09 -0400 |
| commit | 0e81ecf0210ac1770855664753e7afa2280fd3fb (patch) | |
| tree | 6caeaf7a6640df54a5ae4216fb2ad201cf7e081e /drivers/gpu/nvgpu/common | |
| parent | 5248d6b4b5f74a5dca492d7666e80a819734f8da (diff) | |
gpu: nvgpu: gk20a: Fix up qos/sysfs limits
Userspace sysfs limits devfreq->{min|max}_freq and pmqos min/max limits
are treated as the same priority. In case these two ranges don't intersect
prefer the max_freq clamp over the min_freq clamp.
This is done in order to ensure any thermal throttling isn't bypassed by a
userspace sysfs write. MaxQ/MaxP configurations only care about the Fmax
limit and not necessarily Fmin, so preferring max_freq over min_freq is
consistent with what is required.
Bug 1933216
Change-Id: Ie8685306f10dee0f8d340c4b8e0eae533dbfc6ac
Signed-off-by: Sai Gurrappadi <sgurrappadi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1535937
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
Reviewed-by: Aaron Huang <aaronh@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: svc-mobile-misra <svc-mobile-misra@nvidia.com>
Reviewed-by: Deepak Nibade <dnibade@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/common')
0 files changed, 0 insertions, 0 deletions