aboutsummaryrefslogtreecommitdiffstats
path: root/remote-processor/Android.mk
Commit message (Collapse)AuthorAgeFilesLines
* [Makefile] Format variables to lower_snake_caseKevin Rocard2014-02-121-14/+14
| | | | | | | | | | | | | | | | | BZ: 115743 Some variables where not formatted as requested by the coding style. Format them to lower_snake_case. Change-Id: I31c152f161cde469bcd4c00953e95274c60868ca Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/115175 Reviewed-by: Denneulin, Guillaume <guillaume.denneulin@intel.com> Reviewed-by: De Chivre, Renaud <renaud.de.chivre@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* [Makefile] Append "_host" to host modules namesKevin Rocard2014-02-121-1/+1
| | | | | | | | | | | | | | | | | | | | | BZ: 115743 In some parameter framework makefiles, host and target modules (with the same name) are defined in the same file. External prebuilt framework properly handle this case when modules are defined in different Android.mk, but there is a limitation when modules are defined in same Android.mk. Append _host to all host modules. Change-Id: Ib594dabd86617cc40993066338f095b49afb2ea2 Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/113537 Reviewed-by: Denneulin, Guillaume <guillaume.denneulin@intel.com> Reviewed-by: De Chivre, Renaud <renaud.de.chivre@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* Remove no-non-virtual-dtor flagSebastien Gonzalve2014-02-121-3/+0
| | | | | | | | | | | | | | BZ: 111473 The warning non-virtual-dtor should not be ignored for the whole project, but only in the few cases where it it necessary. Change-Id: I0ede82a30f2cd055b789f7fb56104fb227934e6f Signed-off-by: Sebastien Gonzalve <sebastien.gonzalve@intel.com> Signed-off-by: Guilhem IMBERTON <guilhem.imberton@intel.com> Reviewed-on: http://android.intel.com:8080/110191 Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* Change TARGET_ERROR_FLAGS to LOCAL_CFLAGSKevin Rocard2014-02-121-3/+3
| | | | | | | | | | | | | | | | | | BZ: 107991 All plugin Android.mk were copy pasted resulting in use of TARGET_ERROR_FLAGS instead of LOCAL_CFLAGS. Change TARGET_ERROR_FLAGS to LOCAL_CFLAGS Change-Id: I792164e8c056be5dbfee35d07e7dd21b3137f4f6 Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/109723 Reviewed-by: cactus <cactus@intel.com> Reviewed-by: Gonzalve, Sebastien <sebastien.gonzalve@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* PFW: Delete useless libstdc++ includesKevin Rocard2014-02-121-1/+0
| | | | | | | | | | | | | | | | | | BZ: 107991 All plugin Android.mk were copy pasted resulting in duplicated useless libstdc++ includes. Delete the useless makefiles libstdc++ includes. Change-Id: I42bd991c261cd9fe1287b572668c677c42baad8e Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/109279 Reviewed-by: cactus <cactus@intel.com> Reviewed-by: Gonzalve, Sebastien <sebastien.gonzalve@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* [remote-processor] Add support for host buildKevin Rocard2014-02-121-16/+37
| | | | | | | | | | | | | | | | | | BZ: 107991 In order to generate setting xml at build time, one need to build and run PFW environement on host. Add an host compilation target. Change-Id: I50b4ed0d33597db2e485c45cf2229d62b63c805e Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/107269 Reviewed-by: cactus <cactus@intel.com> Reviewed-by: Gonzalve, Sebastien <sebastien.gonzalve@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* PFW: Fix missing space before := in makefilesKevin Rocard2014-02-121-3/+3
| | | | | | | | | | | | | | | | | | BZ: 107991 Some makefile were missing a space before := in makefiles Add a space before := Change-Id: Ie04cd85e3b21a0628f612a374b5c3d294fd724db Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com> Reviewed-on: http://android.intel.com:8080/109305 Reviewed-by: Denneulin, Guillaume <guillaume.denneulin@intel.com> Reviewed-by: Gonzalve, Sebastien <sebastien.gonzalve@intel.com> Reviewed-by: cactus <cactus@intel.com> Tested-by: Dixon, CharlesX <charlesx.dixon@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com>
* parameter-framework: initial commitPatrick Benavoli2011-09-081-0/+39
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>
generated by cgit v1.1 at 2025-01-08 23:45:16 +0000