drm/nouveau/tmr: avoid processing completed alarms when adding a new one
authorBen Skeggs <bskeggs@redhat.com>
Thu, 11 May 2017 07:13:29 +0000 (17:13 +1000)
committerBen Skeggs <bskeggs@redhat.com>
Thu, 11 May 2017 22:32:58 +0000 (08:32 +1000)
commit330bdf62fe6a6c5b99a647f7bf7157107c9348b3
tree1fe7a3da274d6a66fd77d4326704b9232fa3a07c
parent9fc64667ee48c9a25e7dca1a6bcb6906fec5bcc5
drm/nouveau/tmr: avoid processing completed alarms when adding a new one

The idea here was to avoid having to "manually" program the HW if there's
a new earliest alarm.  This was lazy and bad, as it leads to loads of fun
races between inter-related callers (ie. therm).

Turns out, it's not so difficult after all.  Go figure ;)

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Cc: stable@vger.kernel.org
drivers/gpu/drm/nouveau/nvkm/subdev/timer/base.c