From df1668deaa24391bf1686d0abb03f2f904e75ebc Mon Sep 17 00:00:00 2001 From: Seema Khowala Date: Thu, 1 Feb 2018 15:34:40 -0800 Subject: gpu: nvgpu: call nvgpu_init_mm_vars just after probe It is good to init mm vars right after probe as driver is heavily dependent on enabled flags for all kinds of memory related needs Change-Id: I62ca280ff9240649798faa34767f7dc9ea3c0db1 Signed-off-by: Seema Khowala Reviewed-on: https://git-master.nvidia.com/r/1649724 Reviewed-by: svc-mobile-coverity GVS: Gerrit_Virtual_Submit Reviewed-by: Terje Bergstrom Reviewed-by: mobile promotions Tested-by: mobile promotions --- drivers/gpu/nvgpu/common/linux/driver_common.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'drivers/gpu/nvgpu/common/linux/driver_common.c') diff --git a/drivers/gpu/nvgpu/common/linux/driver_common.c b/drivers/gpu/nvgpu/common/linux/driver_common.c index 9df7ea3f..66078a85 100644 --- a/drivers/gpu/nvgpu/common/linux/driver_common.c +++ b/drivers/gpu/nvgpu/common/linux/driver_common.c @@ -223,6 +223,8 @@ int nvgpu_probe(struct gk20a *g, return err; } + nvgpu_init_mm_vars(g); + /* platform probe can defer do user init only if probe succeeds */ err = gk20a_user_init(dev, interface_name, class); if (err) @@ -236,8 +238,6 @@ int nvgpu_probe(struct gk20a *g, } } - nvgpu_init_mm_vars(g); - nvgpu_create_sysfs(dev); gk20a_debug_init(g, debugfs_symlink); -- cgit v1.2.2