Min/max value computation; Tuning lock handling

BZ: 7466

- Min/max values are now correctly computed. They concern integer and fixed point parameters
- tuning mode lock issue solved: created an AutoLock class for safe lock handling
- added configuration files for a demo on Ubuntu environment
- had AMIXER subsystem plugin compliant for derivation
- LPE library: add carriage return on logs
- removed obsolete files
- some cosmetics

Change-Id: Ife7a4799fd48dd4a1ca25dae666c4e453815881e
Orig-Change-Id: I72fc5c1ff6abf638b43266a75bc00e21ad412349
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/16880
Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/parameter/Component.h b/parameter/Component.h
index d43e6e8..e868f62 100644
--- a/parameter/Component.h
+++ b/parameter/Component.h
@@ -30,9 +30,9 @@
  */
 #pragma once
 
-#include "ParameterBlock.h"
+#include "InstanceConfigurableElement.h"
 
-class CComponent : public CParameterBlock
+class CComponent : public CInstanceConfigurableElement
 {
 public:
     CComponent(const string& strName, const CTypeElement* pTypeElement);