diff options
| author | Karol Herbst <[email protected]> | 2016-07-12 21:36:09 +0200 |
|---|---|---|
| committer | Ben Skeggs <[email protected]> | 2016-10-12 17:29:28 +1000 |
| commit | 114653c7593a4dd52cc1721b0d325d43b00e2371 (patch) | |
| tree | eda522fa8354766f79d9fe3bb60e25ec97d371a3 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 08de5743db9250dc915d85f9f7d1a9016a8f8975 (diff) | |
drm/nouveau/volt: Make use of cvb coefficients
I'm quite sure that those coefficients are real close, because while
testing the biggest error compared to nvidia was around -1.5% (biggest
error with right coefficients is 12.5mV / 600mV = 2%).
These coefficients were REed by modifing the voltage map entries and by
calculating the set voltage back until I was able to forecast which voltage
nvidia sets for a given voltage map entry.
With these formulars I am able to precisely predict at which exact
temperature Nvidia down- or upvolts due to a changed therm reading.
That's why I am quite sure these are right, or at least really really
close.
v4: Use better coefficients and speedo.
v5: Add error message when speedo is missing.
Signed-off-by: Karol Herbst <[email protected]>
Reviewed-by: Martin Peres <[email protected]>
Signed-off-by: Ben Skeggs <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions