Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / parameter-framework / 12d9c82b31650d307e3834e435e1f5f54e3832d0
commit12d9c82b31650d307e3834e435e1f5f54e3832d0[log] [tgz]
authorDavid Wagner <david.wagner@intel.com>Mon Apr 20 10:51:29 2015 +0200
committerEric Laurent <elaurent@google.com>Fri Apr 24 13:39:15 2015 -0700
tree870ea4bef509979fb237f32695e8fd3932e2b25a
parentb615ea34d81f426b0b3e2e4f3ffd9b1da34d9b36 [diff]
xml coverage: fix a copy-paste mistake

Commit ccb164c15d0f46fb233b67075f37bede8f8ad855 introduced the possibility to
ignore changes to unknown criterion through an option passed to coverage.py but
a copy-paste mistake swapped the action of this option with the option ignoring
incoherent criterion state changes.

Both flags are set by 'aplog2coverage.sh -f' so the mistake went unnoticed but
it must be fixed nevertheless.

Signed-off-by: David Wagner <david.wagner@intel.com>
1 file changed
tree: 870ea4bef509979fb237f32695e8fd3932e2b25a
  1. bindings/
  2. ctest/
  3. parameter/
  4. remote-process/
  5. remote-processor/
  6. Schemas/
  7. skeleton-subsystem/
  8. support/
  9. test/
  10. tools/
  11. utility/
  12. xmlserializer/
  13. .gitignore
  14. .travis.yml
  15. Android.mk
  16. CMakeLists.txt
  17. COPYING
  18. MODULE_LICENSE_BSD
  19. NOTICE
  20. README.md
README.md

parameter-framework

Build Status Coverage Status

Introduction

The parameter-framework is a plugin-based and rule-based framework for handling parameters. This means that you can:

  1. Describe your system's structure and its parameters (in XML) - aka. What;
  2. Write (in C++) or reuse a backend (aka. plugin) for accessing the parameters that you just described - aka. How;
  3. Define (in XML or in a domain-specific-language) conditions/rules upon which a given parameter must take a given value - aka. When.

What, How, When

Usage examples

Alsa controls on embedded platforms

The parameter-framework can be used to set the value of alsa controls (switches, volumes, etc.) on smartphones/tablets based on parameter-framework rules (in this example, they transcribe use-cases). For accessing parameters (i.e. alsa controls), you may use the alsa plugin.

Parameters in files

The filesystem plugin can be used to write parameters in files. This is particularly useful for files in /sys managing GPIOs.

More details

The parameter-framework's core comes in the form of a shared library. Its client has to provide:

  • configuration files describing the structure of the system to be managed by the parameter-framework and what plugins it must use to read/write into each subsystem;
  • a list of criteria (representing the state of the client) and their possible values;
  • configuration files describing the value that each part of the system (aka parameter) must take - this is done by writing rules based on the criteria described above.

At runtime, the most usual communication between the client and the parameter-framework are:

  1. The update of criteria (that are used in the rules introduced above) and
  2. Update all relevant parameters according to the new criteria values. The parameter-framework uses the appropriate backend for writing the values in each underlying subsystem.

The parameter-framework comes with several tools, including a command-line interface: remote-process.

Going further

See the wiki on github.

Compiling

Run cmake . then make. You may then install libraries, headers and binaries with make install. By default, they are installed under /usr/local on unix OSes; if you want to install them under a custom directory, you may do so by passing it to the cmake . command; e.g.

cmake -DCMAKE_INSTALL_PREFIX=/path/to/custom/install .

Also, CMake can build a project out-of-tree, which is the recommended method:

mkdir /path/to/build/directory
cd /path/to/build/directory
cmake /path/to/parameter-framework/sources
make

After an install you may want to run the parameter-framework tests with make test.