| ef1c51a552368aabbee17c2faf16348b6ee873be |
|
10-Apr-2015 |
David Wagner <david.wagner@intel.com> |
Remove unused CXmlElement::setComment method
Signed-off-by: David Wagner <david.wagner@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 911844b16c6b627f421bc3368de427de3ca9f60c |
|
23-Jul-2014 |
Patrick Benavoli <patrick.benavoli@intel.com> |
Type mismatch corrections (Windows 64 bits)
This patch removes the type mismatch warnings revealed by Windows 64
compiler. Wherever necessary, used size_t type for size related data.
Change-Id: Ie045ce95940cd83fe8d681168ac9526fc6028d43
Signed-off-by: Patrick Benavoli <patrick.benavoli@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 0548523ab6bbca766dcce4be97a0c50efd529d90 |
|
08-Jul-2014 |
Patrick Benavoli <patrick.benavoli@intel.com> |
Adding XML format to Criteria export tuning I/F
BZ: 209937
The "listCriteria" command returns the list of criteria in a human readable
way. However, external tools that require to know this list of criteria have
trouble parsing this output. An XML output would solve the issue.
Changed "listCriteria" command to accept "XML" as first and only argument.
In the end, listCriteria command accepts the 3 following forms:
- listCriteria => will list the criteria states and type content in a human
readable format
- listCriteria csv|CSV => will list the criteria states and type content in a
CSV format
- listCriteria xml|XML => will list the criteria states and type content in an
XML format
Removed python binding accordingly.
Change-Id: Ib060ec0a5d1ff87ba6c25caf4e0d5839a7927715
Signed-off-by: Patrick Benavoli <patrick.benavoli@intel.com>
Signed-off-by: Sebastien Gonzalve <sebastien.gonzalve@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| d9526499d6ab53b7d13d1434f748f6f2161c2e0a |
|
20-Feb-2014 |
Sebastien Gonzalve <oznog@zarb.org> |
Remove using std::XXX from headers
This is a bad practice to have using in headers because it pollutes the
namespace of any user of that header.
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 30095b3c0b84e85caf253a27e41254eaf35e4ca7 |
|
15-Apr-2014 |
Eduardo Mendi <eduardox.mendi@intel.com> |
Fix KW10 issues
BZ: 186081
Due to upgrade klocwork (KW version from 9.6 to 10.0)
new issues have been raised.
This patch fix the new issues raised in PFW.
Change-Id: I54c14e4d6da1c9a5f8d82aec1769a9e7e948db50
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| b76c9d6de717a9a1cfd94e7a8eca7ee4a2035cd7 |
|
05-Feb-2014 |
David Wagner <david.wagner@intel.com> |
Change the license to 3-clause BSD
Add license header in all source files and Makefiles,
Add a "COPYING" file containing the license text.
Signed-off-by: David Wagner <david.wagner@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 326a31df0dd401283de6170ed09bcf605f61ef7d |
|
28-Jun-2012 |
Georges-Henri Baron <georges-henrix.baron@intel.com> |
PFW: Add two commands to print xml settings and structure
BZ: 44910
Creates two commands that can be called through the command
line of the parameter-framework. First command getDomainXML
returns a string containing the xml structure of the
domains, configurations and settings. Second command
getSystemClassXML returns a string containing the xml
structure of all the instantiated parameter with their
attributes.
Change-Id: I9a35333802049a2177b8fc416754fdb67e6efff0
Signed-off-by: Georges-Henri Baron <georges-henrix.baron@intel.com>
Reviewed-on: http://android.intel.com:8080/55155
Reviewed-by: Rocard, KevinX <kevinx.rocard@intel.com>
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 93250d172612c405135d56ffd306deae5ebc6df1 |
|
19-Jul-2012 |
Kevin Rocard <kevinx.rocard@intel.com> |
PFW: Remove names from PFW license header
BZ: 47701
As parameter framework code is proprietary, it should not be signed (patrick Benavoli name inside the header).
Change-Id: I198f2851ee2a6cffed64a552fa399b072a0cbd3e
orig-Change-Id: I335ecce2fa22ad11d6fa24f57c7cbbae3423bf1e
Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com>
Reviewed-on: http://android.intel.com:8080/59560
Reviewed-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 63499d4763e42d76bfd39b79871f611381d2d164 |
|
24-Oct-2011 |
Patrick Benavoli <patrickx.benavoli@intel.com> |
parameter-framework: Sequence
BZ: 13152
- Introduced sequence notion in configurations:
Sequences are configuration specific and are controlled from the Settings
related XML files (order of settings appearance) as well as from the tuning
interface (new commands available to set and get the sequence
(setElementSequence / getElementSequence).
Notes:
- sequences will only matter for domains which new "SequenceAware"
attribute is set to true (false by default). This attribute is also
controlable through the tuning interface (setSequenceAware / getSequenceAware
commands).
- sequence unaware domain configurations will be applied before
sequence aware ones.
To allow for such functionality, the XML for settings format had to be
reworked, leading to an unfortunate compatibility break. However, one benefit
is that now a clear Settings section appears at the bottom of the domain
description, which is easier to maintain than the previous structure where the
settings appeared as sub-nodes of associated elements.
Change-Id: Ic93552fd510ed8847f9c8e7d9d6164f7ea3c8c45
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/22558
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Reviewed-on: http://android.intel.com:8080/26780
Reviewed-by: Barthes, FabienX <fabienx.barthes@intel.com>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 6ba361d96bc2581667b3400f87ff89fae6449e1f |
|
31-Aug-2011 |
Patrick Benavoli <patrickx.benavoli@intel.com> |
parameter-framework: improvements and corrections
BZ: 6721
- Bug correction concerning selection criteria display (inclusive type)
- Adapted XML format to allow for only on parameter to be associated to
a domain
- Removed unused files in parameter project
Change-Id: I9f42d08ff8cb60354714fe3d6b0f0b321ad0a7bf
Orig-Change-Id: I837e553070f5acf2d275082c986ba29433493e31
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/16878
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>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|
| 68a912857707864bbaaff9808717813105072a6e |
|
31-Aug-2011 |
Patrick Benavoli <patrickx.benavoli@intel.com> |
parameter-framework: initial commit
BZ: 6081
Parameter-framework is still-under-development, Intel proprietary,
multi-platform (standard C++, for now only linux, no dependency on
Android) software that allows system-wide parameter management. It
relies on a number of configurations files, from which it knows how
/ when to hand out settings towards the hardware (subsystems) at
runtime.
3 kinds of configuration files are used:
- Structure description files indicating the actual parameter
structure, types, min/max values, data representation.
- Configurable domain description file containing the actual
distribution of parameters over different domains, that is, different
set of configurations, each of which being dynamically activated
based on selection criteria rules that are themselves configurable.
Configurable domains file contain the tuned settings along the tuning
process, that is during the period where the system is being tuned.
- Binary settings file used to store the settings when the tuning
process is complete.
Changing any of those files causes no recompilation of the framework.
This project is based on a open plugin architecture allowing any kind
of subsystems to be handled, whatever their respective Endianness.
It fully relies on the platform SW to provide it with with the
kowledge of exisitng selection criteria (selected device, current
mode), as well as change events that occuring on them, thus
triggering the application of corresponding configuration settings
wherever appropriate.
It supports handling mutliple parameter classes (Audio, Energy
management) through TCP/IP interface.
For now tuning commands can be sent to parameter-framework instances
through a command-line utility, via adb over USB or via ethernet/WIFI.
Change-Id: If7709c464db118f367f953e0824f49cce9fd0402
Orig-Change-Id: I7842e8808a4cfc0c615e0365e6d02101971ae2dc
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/16877
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>
/external/parameter-framework/xmlserializer/XmlElement.cpp
|