pull mode from kernel log for re-analysis
removed one trailing whitespace for kernel submission purposes
v2.3 release
separated ACPI into two events
added support for reading in trace events
added device_pm_report_time to the list of trace events to enable
pushed the callgraph analysis into a separate block in analyzetracelog
add support for reading in all the suspend_resume trace events found
in the trace log.
timeline now graphs trace events discovered in the trace log
added check to see if ftrace file passed in has trace events, and
properly shut off all the actions calculated from dmesg since they
are duplicates
changed the test to see where a trace event action should be place,
now it's placed in the first phase that it overlaps with
changed dmesg based actions to match the naming for traceevent
based actions, and set analyzetracelog to ignore trace events
if the flag isn't enabled
added the kernel patch which enabled trace events for this tool

applied to a kernel source tree like this:
cat config/enable_trace_events_suspend_resume.patch | patch -p1
trace event data expands the timeline start and end if they go
outside the approximated boundaries, basically trace events trump
dmesg
trace event patch now adds these trace events to the tool:

sync_filesystems
freeze_processes
save_nvs_memory
acpi_os_sleep
syscore_suspend
syscore_resume
restore_nvs_memory
thaw_processes
added android support for trace events as well
added a better check for trace events going outside timeline boundaries
v2.4 release
updated the trace event patch
added timestamps to the ftrace output graph