summaryrefslogtreecommitdiffstats
path: root/remote-process
diff options
context:
space:
mode:
authorPatrick Benavoli <patrickx.benavoli@intel.com>2011-08-31 11:23:23 +0200
committerbuildbot <buildbot@intel.com>2011-09-08 06:18:29 -0700
commit68a912857707864bbaaff9808717813105072a6e (patch)
tree81b5bc104eec1f4aab75cc14f262dd9783e49946 /remote-process
parenta929d05b870a8947f272a2b4321d396fee9778c3 (diff)
downloadexternal_parameter-framework-68a912857707864bbaaff9808717813105072a6e.zip
external_parameter-framework-68a912857707864bbaaff9808717813105072a6e.tar.gz
external_parameter-framework-68a912857707864bbaaff9808717813105072a6e.tar.bz2
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>
Diffstat (limited to 'remote-process')
-rw-r--r--remote-process/Android.mk32
-rw-r--r--remote-process/main.cpp111
2 files changed, 143 insertions, 0 deletions
diff --git a/remote-process/Android.mk b/remote-process/Android.mk
new file mode 100644
index 0000000..7f1c59c
--- /dev/null
+++ b/remote-process/Android.mk
@@ -0,0 +1,32 @@
+LOCAL_PATH:= $(call my-dir)
+
+include $(CLEAR_VARS)
+
+LOCAL_MODULE_PATH :=
+
+
+LOCAL_SRC_FILES:= \
+ main.cpp
+
+
+LOCAL_MODULE:= remote-process
+
+LOCAL_MODULE_TAGS := optional
+
+TARGET_ERROR_FLAGS += -Wno-non-virtual-dtor
+
+LOCAL_C_INCLUDES += \
+ external/stlport/stlport/ \
+ bionic/libstdc++ \
+ bionic/
+
+LOCAL_C_INCLUDES += $(LOCAL_PATH)/../remote-processor/
+
+LOCAL_SHARED_LIBRARIES := libstlport libicuuc libremote-processor
+LOCAL_STATIC_LIBRARIES :=
+
+LOCAL_LDLIBS +=
+LOCAL_LDFLAGS +=
+
+include $(BUILD_EXECUTABLE)
+
diff --git a/remote-process/main.cpp b/remote-process/main.cpp
new file mode 100644
index 0000000..51d0fae
--- /dev/null
+++ b/remote-process/main.cpp
@@ -0,0 +1,111 @@
+/* <auto_header>
+ * <FILENAME>
+ *
+ * INTEL CONFIDENTIAL
+ * Copyright © 2011 Intel
+ * Corporation All Rights Reserved.
+ *
+ * The source code contained or described herein and all documents related to
+ * the source code ("Material") are owned by Intel Corporation or its suppliers
+ * or licensors. Title to the Material remains with Intel Corporation or its
+ * suppliers and licensors. The Material contains trade secrets and proprietary
+ * and confidential information of Intel or its suppliers and licensors. The
+ * Material is protected by worldwide copyright and trade secret laws and
+ * treaty provisions. No part of the Material may be used, copied, reproduced,
+ * modified, published, uploaded, posted, transmitted, distributed, or
+ * disclosed in any way without Intel’s prior express written permission.
+ *
+ * No license under any patent, copyright, trade secret or other intellectual
+ * property right is granted to or conferred upon you by disclosure or delivery
+ * of the Materials, either expressly, by implication, inducement, estoppel or
+ * otherwise. Any license under such intellectual property rights must be
+ * express and approved by Intel in writing.
+ *
+ * AUTHOR: Patrick Benavoli (patrickx.benavoli@intel.com)
+ * CREATED: 2011-06-01
+ * UPDATED: 2011-07-27
+ *
+ *
+ * </auto_header>
+ */
+#include <iostream>
+#include <stdlib.h>
+#include "RequestMessage.h"
+#include "AnswerMessage.h"
+#include "ConnectionSocket.h"
+
+using namespace std;
+
+// <program> <target> <port> <cmd> <arg>*
+int main(int argc, char *argv[])
+{
+ // Enough args?
+ if (argc < 4) {
+
+ cerr << "Missing arguments" << endl;
+ cerr << "Usage: " << argv[1] << " <target> <port> <cmd> <arg>*" << endl;
+
+ return -1;
+ }
+ // Get port number
+ uint16_t uiPort = (uint16_t)strtoul(argv[2], NULL, 0);
+
+ // Connect to target
+ CConnectionSocket connectionSocket;
+
+ // Set timeout
+ connectionSocket.setTimeout(5000);
+
+ string strError;
+ // Connect
+ if (!connectionSocket.connect(argv[1], uiPort, strError)) {
+
+ cerr << strError << endl;
+
+ return -2;
+ }
+
+ // Create command message
+ CRequestMessage requestMessage(argv[3]);
+
+ // Add arguments
+ uint32_t uiArg;
+
+ for (uiArg = 4; uiArg < (uint32_t)argc; uiArg++) {
+
+ requestMessage.addArgument(argv[uiArg]);
+ }
+
+ ///// Send command
+ if (!requestMessage.serialize(&connectionSocket, true)) {
+
+ cerr << "Unable to send command to target" << endl;
+
+ return -3;
+ }
+
+ // Create answer message
+ CAnswerMessage answerMessage;
+
+ ///// Get answer
+ if (!answerMessage.serialize(&connectionSocket, false)) {
+
+ cerr << "No answer received from target" << endl;
+
+ return -4;
+ }
+
+ // Success?
+ if (!answerMessage.success()) {
+
+ // Display error answer
+ cerr << answerMessage.getAnswer() << endl;
+ } else {
+
+ // Display success answer
+ cout << answerMessage.getAnswer() << endl;
+ }
+
+ // Program status
+ return answerMessage.success() ? 0 : -5;
+}