On 05/03/17 18:34, Karol Herbst wrote:
This function will be used to update the current clock state.
This will happen for various reasons:
* Temperature changes
* User changes clocking state
* Load changes
Signed-off-by: Karol Herbst
---
drm/nouveau/include/nvkm/subdev/clk.h | 1 +
drm
https://bugs.freedesktop.org/show_bug.cgi?id=99922
--- Comment #10 from kevin@potatofrom.space ---
The patch indeed fixes this issue! The monitors go to sleep and wake up without
problems.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99922
--- Comment #11 from bastian.beisc...@rwth-aachen.de ---
I can also confirm that the patch fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailin
On 05/03/17 18:35, Karol Herbst wrote:
We will access the current set cstate at least every second and this safes
Either "the current ctstate" or "the currently-set cstate", but not a
mix of both :D I prefer the first.
safes -> saves.
us some CPU cycles looking them up every second.
Signe
On 05/03/17 18:35, Karol Herbst wrote:
This makes the code easier, because we can compare the id with
pstate->pstate and safe us the trouble iterating over the entire pstate
saves us from the trouble of iterating over the pstates.
list to match the index.
Signed-off-by: Karol Herbst
Reviewe
On 05/03/17 18:35, Karol Herbst wrote:
The idea is to clear out the saved state, because after a resume we can't
know what the GPU is clocked to. The reclock is triggered by the call to
nvkm_clk_update later in nvkm_clk_init.
Signed-off-by: Karol Herbst
Reviewed-by: Martin Peres
---
drm/nouve
On 05/03/17 18:35, Karol Herbst wrote:
We don't want to change anything on the GPU if it's suspended. Also we
need to increase the refcount on the pm_runtime counter so that the GPU
won't be suspended while reclocking.
Signed-off-by: Karol Herbst
---
drm/nouveau/nvkm/subdev/clk/base.c | 10 +++
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #113 from Lyude Paul ---
Hey, as well even though this is fixed in the development branch I was asked by
one of the other nouveau guys to post this for people running older kernels
since it's easier to backport. This is a very dirty h
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #114 from Lyude Paul ---
Created attachment 130094
--> https://bugs.freedesktop.org/attachment.cgi?id=130094&action=edit
Disable last 512 MiB of VRAM on GTX970
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #115 from Bernie Innocenti ---
I tested the nouveau module built from https://github.com/skeggsb/nouveau on
top of the latest drm-next kernel and I can confirm that it fixes the black
screen issue on my GTX 970 with 4GB of VRAM.
Ben,
10 matches
Mail list logo