diff options
| author | Deepak Nibade <dnibade@nvidia.com> | 2018-07-06 02:29:13 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2018-07-06 11:24:01 -0400 |
| commit | c8347c83697b75823f6e5141b06b8e4669061b99 (patch) | |
| tree | c0628cd0cf64cb7f0e7d8ff37e9982b219664d63 /drivers/gpu/nvgpu/vgpu/gv11b | |
| parent | 0297eed338f9d164a20c1b9224dac7138e152786 (diff) | |
gpu: nvgpu: ring doorbell after enabling TSG
In some use cases client will disable and preempt TSG and then re-enable it
using IOCTLs provided
In case there is only one context getting re-enabled and there is no other job
submission in parallel runlist fetcher will just sleep until doorbell is
received next time
This causes above mentioned test cases to stall after re-enabling TSG until
some one submits a new job and triggers a doorbell
Fix this by explicitly triggering doorbell from gv11b_fifo_enable_tsg() after
we enable all channels in TSG
Bug 2205192
Change-Id: I08e70e3d0f7e4dc6471e63809e246430cc4200c1
Signed-off-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1772378
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/vgpu/gv11b')
0 files changed, 0 insertions, 0 deletions