mirror of
git://nv-tegra.nvidia.com/linux-nvgpu.git
synced 2025-12-25 11:04:51 +03:00
5a5f082d24
With genpd based runtime PM, the device railgating is managed by the PM core and the nvgpu manages the clocks. To suspend/resume the device for idling/unidling while initializing secure alloc, runtime PM will be enabled before init_secure_alloc. nvgpu platform railgate handlers will be only managing the clocks. The clocks and secure alloc initialization was done in platform probe (applicable to tegra). To suspend (railgate and clks disable) and resume cleanly during secure alloc init, the platform probe should happen first that initializes the clocks. Post that device runtime PM will handle the device idle/unidle properly. Hence, move gk20a_tegra_init_secure_alloc to platform late_probe. Runtime PM changes are introduced in the later patches. Bug 200602747 JIRA NVGPU-5356 Change-Id: I5130ff43f7b75ddc51cb7096ba6532b3f5397258 Signed-off-by: Sagar Kamble <skamble@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/2375938 GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: Deepak Nibade <dnibade@nvidia.com> Reviewed-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>