[PATCH 1/5] tests/exynos: add fimg2d performance analysis

2015-03-26 Thread Emil Velikov
On 25/03/15 18:27, Tobias Jakobi wrote: > Hello, > > the new version should fix most of the mentioned issues. > > Tobias Jakobi wrote: >>> As a general note I would recommend keeping statements on separate lines >>> (none of if (foo) far()) as it makes debugging easier. >> OK, changing this. > Ex

[PATCH 1/5] tests/exynos: add fimg2d performance analysis

2015-03-25 Thread Tobias Jakobi
Hello, the new version should fix most of the mentioned issues. Tobias Jakobi wrote: >> As a general note I would recommend keeping statements on separate lines >> (none of if (foo) far()) as it makes debugging easier. > OK, changing this. Except for this, I didn't change it since I don't see the

[PATCH 1/5] tests/exynos: add fimg2d performance analysis

2015-03-22 Thread Tobias Jakobi
Hello Emil, Emil Velikov wrote: > Might I suggest that we treat this (and your follow up utility) as a > test ? I.e. use > > if HAVE_INSTALL_TESTS > bin_PROGRAMS = \ > exynos_fimg2d_perf > else > noinst_PROGRAMS = \ > exynos_fimg2d_perf > endif > > and amend the block below appropri

[PATCH 1/5] tests/exynos: add fimg2d performance analysis

2015-03-22 Thread Emil Velikov
On 20/03/15 22:25, Tobias Jakobi wrote: > Currently only fast solid color clear performance is measured. > A large buffer is allocated and solid color clear operations > are executed on it with randomly chosen properties (position > and size of the region, clear color). Execution time is > measured

[PATCH 1/5] tests/exynos: add fimg2d performance analysis

2015-03-20 Thread Tobias Jakobi
Currently only fast solid color clear performance is measured. A large buffer is allocated and solid color clear operations are executed on it with randomly chosen properties (position and size of the region, clear color). Execution time is measured and output together with the amount of pixels pro