search for: hwom

...s returning an error (we could return -EBUSY or somehting instead, granted), yet if the device is shadowed, getting a sane temp value out of is seems unlikely to me! Greetings, Tobias On 1/26/18 12:40 PM, Karol Herbst wrote: > no, we can't do that. We actually have to prevent this from hwom. The > issue here is, that the reg read returns 0xffffffff and parsing that > is the first step in the first place. > > On Thu, Jan 25, 2018 at 7:16 PM, Tobias Klausmann > <tobias.johannes.klausmann at mni.thm.de> wrote: >> This fixes wrong temperature outputs e.g. 511°C...

This fixes wrong temperature outputs e.g. 511°C if the card is asleep. Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- drivers/gpu/drm/nouveau/nvkm/subdev/therm/gp100.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/therm/gp100.c b/drivers/gpu/drm/nouveau/nvkm/subdev/therm/gp100.c index

no, we can't do that. We actually have to prevent this from hwom. The issue here is, that the reg read returns 0xffffffff and parsing that is the first step in the first place. On Thu, Jan 25, 2018 at 7:16 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > This fixes wrong temperature outputs e.g. 511°C if the card is asleep. >...

...hting instead, granted), yet if the > device is shadowed, getting a sane temp value out of is seems unlikely to > me! > > Greetings, > > Tobias > > > On 1/26/18 12:40 PM, Karol Herbst wrote: >> >> no, we can't do that. We actually have to prevent this from hwom. The >> issue here is, that the reg read returns 0xffffffff and parsing that >> is the first step in the first place. >> >> On Thu, Jan 25, 2018 at 7:16 PM, Tobias Klausmann >> <tobias.johannes.klausmann at mni.thm.de> wrote: >>> >>> This fixes...