LineageOS/android_hardware_libhardware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

context hub: add reboot command/response and reboot notification

Browse Source 
Change-Id: I20447c0b20eb2d6c4019f8038cb19749fee0126b
This commit is contained in:
Alexey Polyudov
2016-07-10 14:26:18 -07:00
parent 4a2683f893
commit 966a9f3f78
1 changed files with 22 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
include/hardware/context_hub.h
View File

@@ -357,6 +357,27 @@ struct query_apps_request_t {
* Response : struct mem_range_t[] * Response : struct mem_range_t[]
*/ */
/**
* CONTEXT_HUB_OS_REBOOT
* Reboots context hub OS, restarts all the nanoApps.
* No reboot notification is sent to nanoApps; reboot happens immediately and
* unconditionally; all volatile FW state and any data is lost as a result
*
* Payload : none
*
* Response : status_response_t
* On receipt of a successful response, it is
* expected that
*
* i) system reboot has completed;
* status contains reboot reason code (platform-specific)
*
* Unsolicited response:
* System may send unsolicited response at any time;
* this should be interpreted as FW reboot, and necessary setup
* has to be done (same or similar to the setup done on system boot)
*/
/** /**
* All communication between the context hubs and the Context Hub Service is in * All communication between the context hubs and the Context Hub Service is in
* the form of messages. Some message types are distinguished and their * the form of messages. Some message types are distinguished and their
@@ -372,6 +393,7 @@ typedef enum {
CONTEXT_HUB_UNLOAD_APP = 4, // Unload a specified app CONTEXT_HUB_UNLOAD_APP = 4, // Unload a specified app
CONTEXT_HUB_QUERY_APPS = 5, // Query for app(s) info on hub CONTEXT_HUB_QUERY_APPS = 5, // Query for app(s) info on hub
CONTEXT_HUB_QUERY_MEMORY = 6, // Query for memory info CONTEXT_HUB_QUERY_MEMORY = 6, // Query for memory info
CONTEXT_HUB_OS_REBOOT = 7, // Request to reboot context HUB OS
} hub_messages_e; } hub_messages_e;
#define CONTEXT_HUB_TYPE_PRIVATE_MSG_BASE 0x00400 #define CONTEXT_HUB_TYPE_PRIVATE_MSG_BASE 0x00400