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 <seemaj@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1649724
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>
This commit is contained in:
Seema Khowala
2018-02-01 15:34:40 -08:00
committed by mobile promotions
parent ff5b12fffd
commit df1668deaa

View File

@@ -223,6 +223,8 @@ int nvgpu_probe(struct gk20a *g,
return err; return err;
} }
nvgpu_init_mm_vars(g);
/* platform probe can defer do user init only if probe succeeds */ /* platform probe can defer do user init only if probe succeeds */
err = gk20a_user_init(dev, interface_name, class); err = gk20a_user_init(dev, interface_name, class);
if (err) if (err)
@@ -236,8 +238,6 @@ int nvgpu_probe(struct gk20a *g,
} }
} }
nvgpu_init_mm_vars(g);
nvgpu_create_sysfs(dev); nvgpu_create_sysfs(dev);
gk20a_debug_init(g, debugfs_symlink); gk20a_debug_init(g, debugfs_symlink);