msm: kgsl: Do not capture DTCM on gmu boot failure

Accessing DTCM can cause NoC error sometimes if GMU is accessing
any of its TCMs at the same time as host.

Change-Id: I3d7a3169620854dbd659f378c216a7b15435c914
Signed-off-by: Harshdeep Dhatt <hdhatt@codeaurora.org>
This commit is contained in:
Harshdeep Dhatt 2020-07-17 13:14:42 -06:00
commit f4721b63c8

View file

@ -457,15 +457,8 @@ static int a6xx_gmu_device_start(struct adreno_device *adreno_dev)
if (timed_poll_check(device,
A6XX_GMU_CM3_FW_INIT_RESULT,
val, GMU_START_TIMEOUT, mask)) {
u32 val;
/*
* The breadcrumb is written to a gmu virtual mapping
* which points to dtcm byte offset 0x3fdc.
*/
gmu_core_regread(device,
A6XX_GMU_CM3_DTCM_START + (0x3fdc >> 2), &val);
dev_err(&gmu->pdev->dev, "GMU doesn't boot: 0x%x\n", val);
dev_err(&gmu->pdev->dev, "GMU doesn't boot\n");
gmu_fault_snapshot(device);
return -ETIMEDOUT;
}