diff options
author | Deepak Nibade <dnibade@nvidia.com> | 2015-09-10 12:12:47 -0400 |
---|---|---|
committer | Terje Bergstrom <tbergstrom@nvidia.com> | 2015-10-12 11:58:35 -0400 |
commit | 1cf6539990dccd4c7a94154cd75d4c257ed39f37 (patch) | |
tree | 484363e821eb38100bd357d9fe221c6405d0600c /drivers/gpu/nvgpu/gm20b/hw_pbdma_gm20b.h | |
parent | 960552df3ef3f270bce64ed00104dce300531369 (diff) |
gpu: nvgpu: rework secure_page allocation path
Currently, if can_railgate = false, then we have below
sequence to allocate secure_page
- unrailgate GPU (forever)
- reset_assert()
- allocate secure_page
- reset_deassert()
But if we allocate secure page even before unrailgating GPU
for first time, then we can avoid reset_assert()/deassert()
calls since GPU should already be in reset/railgated at
boot time
hence, rework this sequence as below
- init required mutex, set platform->reset_control
- allocate secure page (GPU should already be in reset
at this point)
- gk20a_pm_init() which unrailgates GPU in case of
can_railgate = false
Bug 200137963
Bug 1678611
Change-Id: I79d0543bb5cf1eaf1009e1e6ac142532d84514a5
Signed-off-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-on: http://git-master/r/797153
(cherry picked from commit 368004501943d38c003747f6bec0384fed57ee65)
Reviewed-on: http://git-master/r/816005
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gm20b/hw_pbdma_gm20b.h')
0 files changed, 0 insertions, 0 deletions