blob: 79054d2070fbaaac25160ab03ec9e02c68ac1527 [file] [log] [blame]
Ashutosh Joshi8c3c46d2016-01-08 16:09:11 -08001/*
2 * Copyright (C) 2016 The Android Open Source Project
3 *
4 * Licensed under the Apache License, Version 2.0 (the "License");
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
7 *
8 * http://www.apache.org/licenses/LICENSE-2.0
9 *
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an "AS IS" BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
15 */
16
17#ifndef CONTEXT_HUB_H
18#define CONTEXT_HUB_H
19
20#include <stdint.h>
21#include <sys/cdefs.h>
22#include <sys/types.h>
23
24#include <hardware/hardware.h>
25
26/**
27 * This header file defines the interface of a Context Hub Implementation to
28 * the Android service exposing Context hub capabilities to applications.
29 * The Context hub is expected to a low power compute domain with the following
30 * defining charecteristics -
31 *
32 * 1) Access to sensors like accelerometer, gyroscope, magenetometer.
33 * 2) Access to radios like GPS, Wifi, Bluetooth etc.
34 * 3) Access to low power audio sensing.
35 *
36 * Implementations of this HAL can add additional sensors not defined by the
37 * Android API. Such information sources shall be private to the implementation.
38 *
39 * The Context Hub HAL exposes the construct of code download. A piece of binary
40 * code can be pushed to the context hub through the supported APIs.
41 *
42 * This version of the HAL designs in the possibility of multiple context hubs.
43 */
44
45__BEGIN_DECLS
46
47/*****************************************************************************/
48
Greg Kaiser5600a6a2016-03-28 09:06:56 -070049#define CONTEXT_HUB_HEADER_MAJOR_VERSION 1
50#define CONTEXT_HUB_HEADER_MINOR_VERSION 0
51#define CONTEXT_HUB_DEVICE_API_VERSION \
52 HARDWARE_DEVICE_API_VERSION(CONTEXT_HUB_HEADER_MAJOR_VERSION, \
53 CONTEXT_HUB_HEADER_MINOR_VERSION)
54
55#define CONTEXT_HUB_DEVICE_API_VERSION_1_0 HARDWARE_DEVICE_API_VERSION(1, 0)
Ashutosh Joshi8c3c46d2016-01-08 16:09:11 -080056
57/**
58 * The id of this module
59 */
60#define CONTEXT_HUB_MODULE_ID "context_hub"
61
62/**
63 * Name of the device to open
64 */
65#define CONTEXT_HUB_HARDWARE_POLL "ctxt_poll"
66
67/**
68 * Memory types for code upload. Device-specific. At least HUB_MEM_TYPE_MAIN must be supported
69 */
70#define HUB_MEM_TYPE_MAIN 0
71#define HUB_MEM_TYPE_SECONDARY 1
72#define HUB_MEM_TYPE_TCM 2
73
74
75#define HUB_MEM_TYPE_FIRST_VENDOR 0x80000000ul
76
77
78/**
79 * Other memory types (likely not writeable, informational only)
80 */
81#define HUB_MEM_TYPE_BOOTLOADER 0xfffffffful
82#define HUB_MEM_TYPE_OS 0xfffffffeul
83#define HUB_MEM_TYPE_EEDATA 0xfffffffdul
84#define HUB_MEM_TYPE_RAM 0xfffffffcul
85
86/**
87 * Types of memory blocks on the context hub
88 * */
89#define MEM_FLAG_READ 0x1 // Memory can be written to
90#define MEM_FLAG_WRITE 0x2 // Memory can be written to
91#define MEM_FLAG_EXEC 0x4 // Memory can be executed from
92
93/**
94 * The following structure defines each memory block in detail
95 */
96struct mem_range_t {
97 uint32_t total_bytes;
98 uint32_t free_bytes;
99 uint32_t type; // HUB_MEM_TYPE_*
100 uint32_t mem_flags; // MEM_FLAG_*
101};
102
103
104/**
105 * App names may be strings, bytes, uints, etc. This caovers all types of app names
106 */
107struct hub_app_name_t {
108 uint32_t app_name_len;
109 const void *app_name;
110};
111
112struct hub_app_info {
113 const struct hub_app_name_t *name;
114 uint32_t version;
115 uint32_t num_mem_ranges;
116 const struct mem_range_t *mem_usage;
117};
118
119/**
120 * Following enum defines the types of sensors that a hub may declare support
121 * for. Declaration for support would mean that the hub can access and process
122 * data from that particular sensor type.
123 */
124
125typedef enum {
126 CONTEXT_SENSOR_RESERVED, // 0
127 CONTEXT_SENSOR_ACCELEROMETER, // 1
128 CONTEXT_SENSOR_GYROSCOPE, // 2
129 CONTEXT_SENSOR_MAGNETOMETER, // 3
130 CONTEXT_SENSOR_BAROMETER, // 4
131 CONTEXT_SENSOR_PROXIMITY_SENSOR, // 5
132 CONTEXT_SENSOR_AMBIENT_LIGHT_SENSOR, // 6
133
134 CONTEXT_SENSOR_GPS = 0x100, // 0x100
135 // Reserving this space for variants on GPS
136 CONTEXT_SENSOR_WIFI = 0x200, // 0x200
137 // Reserving this space for variants on WIFI
138 CONTEXT_SENSOR_AUDIO = 0x300, // 0x300
139 // Reserving this space for variants on Audio
140 CONTEXT_SENSOR_CAMERA = 0x400, // 0x400
141 // Reserving this space for variants on Camera
142 CONTEXT_SENSOR_BLE = 0x500, // 0x500
143
144 CONTEXT_SENSOR_MAX = 0xffffffff, //make sure enum size is set
145} context_sensor_e;
146
147/**
148 * Sensor types beyond CONTEXT_HUB_TYPE_PRIVATE_SENSOR_BASE are custom types
149 */
150#define CONTEXT_HUB_TYPE_PRIVATE_SENSOR_BASE 0x10000
151
152/**
153 * The following structure describes a sensor
154 */
155struct physical_sensor_description_t {
156 uint32_t sensor_type; // From the definitions above eg: 100
157 const char *type_string; // Type as a string. eg: "GPS"
158 const char *name; // Identifier eg: "Bosch BMI160"
159 const char *vendor; // Vendor : eg "STM"
160 uint32_t version; // Version : eg 0x1001
Greg Kaisere78619b2016-03-03 11:40:03 -0800161 uint32_t fifo_reserved_count; // Batching possible in hardware. Please
Ashutosh Joshi8c3c46d2016-01-08 16:09:11 -0800162 // note that here hardware does not include
Greg Kaisere78619b2016-03-03 11:40:03 -0800163 // the context hub itself. Thus, this
Ashutosh Joshi8c3c46d2016-01-08 16:09:11 -0800164 // definition may be different from say the
165 // number advertised in the sensors HAL
166 // which allows for batching in a hub.
167 uint32_t fifo_max_count; // maximum number of batchable events.
168 uint64_t min_delay_ms; // in milliseconds, corresponding to highest
169 // sampling freq.
170 uint64_t max_delay_ms; // in milliseconds, corresponds to minimum
171 // sampling frequency
172 float peak_power_mw; // At max frequency & no batching, power
173 // in milliwatts
174};
175
176struct connected_sensor_t {
177 uint32_t sensor_id; // identifier for this sensor
178
179 /* This union may be extended to other sensor types */
180 union {
181 struct physical_sensor_description_t physical_sensor;
182 };
183};
184
185
186
187/**
188 * Messages of this length or less must be supported by all implementations,
189 * longer lengths are supported up to max_supported_msg_len. This is exposed
190 * to third party apps, and since we do not know their msg data formats we
191 * cannot fragment for them. Our own messages are allowed to be bigger and
192 * this HAL will fragment as needed. "Our own" messages are messaegs defined
193 * in this file.
194 */
195#define HUB_REQUIRED_SUPPORTED_MSG_LEN 128
196
197struct hub_message_t {
198 const struct hub_app_name_t *app; /* To/From this nanoapp */
199 uint32_t message_type;
200 uint32_t message_len;
201 const void *message;
202};
203
204
205/**
206 * Definition of a context hub. A device may contain more than one low
207 * power domain. In that case, please add an entry for each hub. However,
208 * it is perfectly OK for a device to declare one context hub and manage
209 * them internally as several
210 */
211
212struct context_hub_t {
213 const char *name; // descriptive name eg: "Awesome Hub #1"
214 const char *vendor; // hub hardware vendor eg: "Qualcomm"
215 const char *toolchain; // toolchain to make binaries eg:"gcc ARM"
216 uint32_t platform_version; // Version of the hardware : eg 0x20
217 uint32_t toolchain_version; // Version of the toolchain : eg: 0x484
218 uint32_t hub_id; // a device unique id for this hub
219
220 float peak_mips; // Peak MIPS platform can deliver
221 float stopped_power_draw_mw; // if stopped, retention power, milliwatts
222 float sleep_power_draw_mw; // if sleeping, retention power, milliwatts
223 float peak_power_draw_mw; // for a busy CPUm power in milliwatts
224
225 const struct connected_sensor_t *connected_sensors; // array of connected sensors
226 uint32_t num_connected_sensors; // number of connected sensors
227
228 uint32_t max_supported_msg_len;
229 const struct hub_app_name_t *os_app_name; /* send msgs here for OS functions */
230};
231
232/**
233 * All communication between the context hubs and the Context Hub Service is in
234 * the form of messages. Some message types are distinguished and their
235 * Semantics shall be well defined.
236 * Custom message types should be defined starting above
237 * CONTEXT_HUB_PRIVATE_MSG_BASE
238 */
239
240typedef enum {
241 CONTEXT_HUB_APPS_ENABLE = 1, // 1: Enables the loaded nano-apps
242 CONTEXT_HUB_APPS_DISABLE, // 2: Disables any loaded nano-apps
243 CONTEXT_HUB_LOAD_APP, // 3: Load a supplied app
244 CONTEXT_HUB_UNLOAD_APP, // 4: Unload a specified app
245 CONTEXT_HUB_QUERY_APPS, // 5: Query for apps info on hub (gets struct hub_app_info[])
246 CONTEXT_HUB_QUERY_MEMORY, // 5: Query for memory info (gets struct mem_range_t[])
247 CONTEXT_HUB_LOAD_OS, // 6: Load up OS update
248} hub_messages_e;
249
250#define CONTEXT_HUB_TYPE_PRIVATE_MSG_BASE 0x10000
251
252
253/**
254 * A callback registers with the context hub service to pass messages
255 * coming from the hub to the service/clients.
256 */
257typedef int context_hub_callback(uint32_t hub_id, const struct hub_message_t *rxed_msg, void *cookie);
258
259
260/**
261 * Every hardware module must have a data structure named HAL_MODULE_INFO_SYM
262 * and the fields of this data structure must begin with hw_module_t
263 * followed by module specific information.
264 */
265struct context_hub_module_t {
266 struct hw_module_t common;
267
268 /**
269 * Enumerate all available hubs.The list is returned in "list".
Dmitry Grinberg90e91402016-02-04 16:43:41 -0800270 * @return result : number of hubs in list or error (negative)
Ashutosh Joshi8c3c46d2016-01-08 16:09:11 -0800271 *
272 * This method shall be called at device bootup.
273 */
274 int (*get_hubs)(struct context_hub_module_t* module, const struct context_hub_t ** list);
275
276 /**
277 * Registers a callback for the HAL implementation to communicate
278 * with the context hub service.
279 * @return result : 0 if successful, error code otherwise
280 */
281 int (*subscribe_messages)(uint32_t hub_id, context_hub_callback cbk, void *cookie);
282
283 /**
284 * Send a message to a hub
285 * @return result : 0 if successful, error code otherwise
286 */
287 int (*send_message)(uint32_t hub_id, const struct hub_message_t *msg);
288
289};
290
291__END_DECLS
292
293#endif // CONTEXT_HUB_SENSORS_INTERFACE_H