devfreq: add devfreq devices stats support

add window to show frequency stats for devfreq devices

Signed-off-by: Rajagopal Venkat <rajagopal.venkat@gmail.com>
Signed-off-by: Sanjay Singh Rawat <sanjay.rawat@linaro.org>
Revert "devfreq: add devfreq devices stats support"

This reverts commit 88d4674ec29bf74bc7a3aa6ab8ef8a57660ccfa3. Will be
replaced for version 4 of the same commit.
devfreq: add devfreq devices stats support

add window to show frequency stats for devfreq devices

Signed-off-by: Rajagopal Venkat <rajagopal.venkat@gmail.com>
Signed-off-by: Sanjay Singh Rawat <sanjay.rawat@linaro.org>
Properly cleaning up the display tabs

This patch properly cleans up the display tabs so that none of the tab
data is being leaked between refresh changes

Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com>

v2: rebased atop 41c54e8; there's a bug here

Signed-off-by: Joe Konno <joe.konno@intel.com>
Remove another memory leak

Pointer gets over written without ever being properly cleaned up.  This
should solve that problem.

v2: rebased atop 41c54e8, do not delete window in clear_tunables() to
prevent double-free in close_display().

Signed-off-by: Joe Konno <joe.konno@intel.com>
Mark pretty_print_init as initialized

There is a check for it, but it's never actually set.  Now it's set.

v2: rebased atop 41c54e8

Signed-off-by: Joe Konno <joe.konno@intel.com>
Adding a clean_shutdown function

Function is designed to be a on stop place to clean up the entire
application at shutdown time.

v2: rebased atop 41c54e8

Signed-off-by: Joe Konno <joe.konno@intel.com>
Removing a documented memory leak

A non-elegant solution to it, but it works well enough to remove the
documented memory leak.  Proves to provide a much larger impact on
memory constrained systems.

v2: rebased atop 41c54e8

Signed-off-by: Joe Konno <joe.konno@intel.com>
Addede support for Intel platforms

Enable PowerTOP support for: HSX, HSW, AVN, BDX, and BDX-DE.

Signed-off-by: Alexandra Yates <alexandra.yates@linux.intel.com>
Deletion of unnecessary checks before specific function calls

The function "free" is documented in the way that no action shall occur for
a passed null pointer. It is therefore not needed that a function caller
repeats a corresponding check.
http://stackoverflow.com/questions/18775608/free-a-null-pointer-anyway-or-check-first

Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>