Age | Commit message (Collapse) | Author |
|
|
|
|
|
Run is a very generic and inappropriate name for an object that parses
the result of ftrace into a form consumable by python. Rename it to
FTrace in preparation for its generalization.
|
|
Change-Id: I7e0e34c9f5565e34629683bb29ab25cf5e737088
|
|
Change-Id: Ie505af7efb7526f94b1cc9e37195cbd2e0451b9d
|
|
Change-Id: Ia27765444594448313b955a7808b3532fb89df50
|
|
They are missing and we need them if we want to opensource this.
Change-Id: I456ecd5ac5e33c7ada234f490389572d8932090b
Signed-off-by: Javi Merino <javi.merino@arm.com>
|
|
We now have trace for devfreq cooling, for the gpu, so get new trace
data that contains it. Fix the tests that broke because of the new
data.
Change-Id: I9e0e7e575fa69e40a8811f6979f9f50f5ff71106
|
|
Two keys in the cpu cooling device have changed, so update the trace
with that information and fix the tests that broke because of that.
|
|
Trace classes are about to be removed from the directly exposed module
classes so don't make tests rely on it. Move a couple of checks from
ThermalGovernor tests to the Run() tests as it's testing basic
functionality that really belongs to the Run() class now.
|
|
|
|
Memoize the PIDController object and close all plots before plotting
new.
|
|
Always create the data_frame when constructing the object. There's no
point deferring it, you almost always need it.
|
|
And a new trace file
|
|
|
|
New format trace for the input power. Now it's a proper trace event
and not a bprint.
|
|
|
|
|