Skip to content
Snippets Groups Projects
Commit ed1ce8ad authored by Pratik Patel's avatar Pratik Patel
Browse files

linux-ramdump-parser-v2: don't print regs for check-for-watchdog

No need to print regs for --check-for-watchdog since they are
getting printed via --parse-debug-image after checking proper
magic values. Also skip printing whether wdog occurred for
targets that use newer memory dump table format since it will be
covered by the per cpu status field.

Change-Id: I9489006e467ccdb452251abd6f084d05b54ef500
parent 31647feb
No related branches found
No related tags found
No related merge requests found
......@@ -306,6 +306,9 @@ class TZRegDump(RamParser):
return True
def parse(self):
if self.ramdump.addr_lookup('memdump'):
return None
ebi_addr = self.ramdump.read_tz_offset()
if ebi_addr is None:
......@@ -323,22 +326,6 @@ class TZRegDump(RamParser):
'[!!!!] Read {0:x} from IMEM successfully!'.format(ebi_addr))
print_out_str('[!!!!] An FIQ occured on the system!')
# The debug image will be responsible for printing out the register
# information, no need to print it twice
if self.ramdump.is_config_defined('CONFIG_MSM_DEBUG_IMAGE'):
print_out_str(
'[!!!!] Debug image was enabled, the contexts will be printed there')
return
regs = self.init_regs(ebi_addr)
if regs is False:
print_out_str('!!! Could not get registers from TZ dump')
return
for i in range(self.ncores):
self.dump_core_pc(i)
self.dump_all_regs()
def get_wdog_timing(ramdump):
jiffies_addr = ramdump.addr_lookup('jiffies')
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment