km: (HACK): map entire SGX address range

SGX needs entire register address range to be mapped. SoC integration only
requires GPU_WRAPPER range for hwmod.

Specify the GPU_WRAPPER range in DT. Map the entire range
irrespective of what is defined in DT.

The right way to do it would be through register definitions in DT that can
work for both hwmod as well as the driver.

This is a HACK patch and should be addressed for DDK migration.

Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/eurasia_km/services4/system/omap/sysconfig.c b/eurasia_km/services4/system/omap/sysconfig.c
index 3ebb7c8..426fa87 100644
--- a/eurasia_km/services4/system/omap/sysconfig.c
+++ b/eurasia_km/services4/system/omap/sysconfig.c
@@ -210,7 +210,7 @@ static PVRSRV_ERROR SysLocateDevices(SYS_DATA *psSysData)
                 return PVRSRV_ERROR_INVALID_DEVICE;
         }
         
-        gsSGXDeviceMap.sRegsSysPBase.uiAddr = dev_res->start;
+        gsSGXDeviceMap.sRegsSysPBase.uiAddr = SYS_OMAP_SGX_REGS_SYS_PHYS_BASE;
         gsSGXDeviceMap.sRegsCpuPBase =
                 SysSysPAddrToCpuPAddr(gsSGXDeviceMap.sRegsSysPBase);
         PVR_TRACE(("SGX register base: 0x%lx", (unsigned long)gsSGXDeviceMap.sRegsCpuPBase.uiAddr));