msm: kgsl: Don't read stale crashdumper data
After the crashdumper runs once, and the user sets the snapshot_crashdumper sysfs node to 0, it is possible that stale data is saved off into the snapshot. Check the value of the sysfs node at the appropriate place to force a re-read of the data through the legacy path. Change-Id: Icf27c39b68d786003c33fd0eb22bd3e8b9a036be Signed-off-by: Lynus Vaz <lvaz@codeaurora.org>
This commit is contained in:
parent
b95d667366
commit
1e450489ff
1 changed files with 3 additions and 2 deletions
|
@ -765,6 +765,8 @@ static void _a5xx_do_crashdump(struct kgsl_device *device)
|
|||
|
||||
crash_dump_valid = false;
|
||||
|
||||
if (!device->snapshot_crashdumper)
|
||||
return;
|
||||
if (capturescript.gpuaddr == 0 || registers.gpuaddr == 0)
|
||||
return;
|
||||
|
||||
|
@ -870,8 +872,7 @@ void a5xx_snapshot(struct adreno_device *adreno_dev,
|
|||
ARRAY_SIZE(a5xx_vbif_snapshot_registers));
|
||||
|
||||
/* Try to run the crash dumper */
|
||||
if (device->snapshot_crashdumper)
|
||||
_a5xx_do_crashdump(device);
|
||||
_a5xx_do_crashdump(device);
|
||||
|
||||
kgsl_snapshot_add_section(device, KGSL_SNAPSHOT_SECTION_REGS,
|
||||
snapshot, a5xx_snapshot_registers, NULL);
|
||||
|
|
Loading…
Add table
Reference in a new issue