drm/nouveau/ltc/gf100: use more reasonable timeout value
LTC operations timeout was set to 2ms, which may be too low for devices that run at very low clocks (e.g. GM20B) and trigger timeout messages. Set the timeout to the default 2s. Also remove the redundant error messages since nvkm_wait_msec() will already display a warning. Signed-off-by: Alexandre Courbot <acourbot@nvidia.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
This commit is contained in:
parent
a2e435a1b0
commit
ab08f38cac
|
@ -129,9 +129,7 @@ gf100_ltc_invalidate(struct nvkm_ltc *ltc)
|
||||||
s64 taken;
|
s64 taken;
|
||||||
|
|
||||||
nvkm_wr32(device, 0x70004, 0x00000001);
|
nvkm_wr32(device, 0x70004, 0x00000001);
|
||||||
taken = nvkm_wait_msec(device, 2, 0x70004, 0x00000003, 0x00000000);
|
taken = nvkm_wait_msec(device, 2000, 0x70004, 0x00000003, 0x00000000);
|
||||||
if (taken < 0)
|
|
||||||
nvkm_warn(<c->subdev, "LTC invalidate timeout\n");
|
|
||||||
|
|
||||||
if (taken > 0)
|
if (taken > 0)
|
||||||
nvkm_debug(<c->subdev, "LTC invalidate took %lld ns\n", taken);
|
nvkm_debug(<c->subdev, "LTC invalidate took %lld ns\n", taken);
|
||||||
|
@ -144,9 +142,7 @@ gf100_ltc_flush(struct nvkm_ltc *ltc)
|
||||||
s64 taken;
|
s64 taken;
|
||||||
|
|
||||||
nvkm_wr32(device, 0x70010, 0x00000001);
|
nvkm_wr32(device, 0x70010, 0x00000001);
|
||||||
taken = nvkm_wait_msec(device, 2, 0x70010, 0x00000003, 0x00000000);
|
taken = nvkm_wait_msec(device, 2000, 0x70010, 0x00000003, 0x00000000);
|
||||||
if (taken < 0)
|
|
||||||
nvkm_warn(<c->subdev, "LTC flush timeout\n");
|
|
||||||
|
|
||||||
if (taken > 0)
|
if (taken > 0)
|
||||||
nvkm_debug(<c->subdev, "LTC flush took %lld ns\n", taken);
|
nvkm_debug(<c->subdev, "LTC flush took %lld ns\n", taken);
|
||||||
|
|
Loading…
Reference in New Issue