mirror of
git://nv-tegra.nvidia.com/linux-nvgpu.git
synced 2025-12-22 17:36:20 +03:00
gpu: nvgpu: don't build sw semas for dgpu
Make tu104's sema cmd HAL ops depend on CONFIG_NVGPU_SW_SEMAPHORE in addition to the kernel mode submit flag. Drop CONFIG_NVGPU_SW_SEMAPHORE from NVGPU_FORCE_DGPU_SAFETY_PROFILE. Semaphore-based synchronization is not actually needed for dgpu. Jira NVGPU-4548 Change-Id: I3fe066dbeb68295dfc4bbe09256ff6a20c892c2f Signed-off-by: Konsta Hölttä <kholtta@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/2318737 Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: svc-mobile-misra <svc-mobile-misra@nvidia.com> Reviewed-by: svc-mobile-cert <svc-mobile-cert@nvidia.com> Reviewed-by: Deepak Nibade <dnibade@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
This commit is contained in:
committed by
Alex Waterman
parent
9846573d64
commit
db9c1b1f97
@@ -105,10 +105,6 @@ NVGPU_COMMON_CFLAGS += -DCONFIG_NVGPU_KERNEL_MODE_SUBMIT
|
||||
CONFIG_NVGPU_FALCON_NON_FUSA := 1
|
||||
NVGPU_COMMON_CFLAGS += -DCONFIG_NVGPU_FALCON_NON_FUSA
|
||||
|
||||
# nvgpu_semaphore_get_value
|
||||
CONFIG_NVGPU_SW_SEMAPHORE :=1
|
||||
NVGPU_COMMON_CFLAGS += -DCONFIG_NVGPU_SW_SEMAPHORE
|
||||
|
||||
CONFIG_NVGPU_GR_FALCON_NON_SECURE_BOOT := 1
|
||||
NVGPU_COMMON_CFLAGS += -DCONFIG_NVGPU_GR_FALCON_NON_SECURE_BOOT
|
||||
|
||||
|
||||
@@ -1060,7 +1060,8 @@ static const struct gpu_ops tu104_ops = {
|
||||
.get_sync_ro_map = gv11b_syncpt_get_sync_ro_map,
|
||||
},
|
||||
#endif /* CONFIG_TEGRA_GK20A_NVHOST */
|
||||
#ifdef CONFIG_NVGPU_KERNEL_MODE_SUBMIT
|
||||
#if defined(CONFIG_NVGPU_KERNEL_MODE_SUBMIT) && \
|
||||
defined(CONFIG_NVGPU_SW_SEMAPHORE)
|
||||
.sema = {
|
||||
.get_wait_cmd_size = gv11b_sema_get_wait_cmd_size,
|
||||
.get_incr_cmd_size = gv11b_sema_get_incr_cmd_size,
|
||||
|
||||
Reference in New Issue
Block a user