1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
|
Controler AAAA(AGL Advance Audio Controler) and more.
------------------------------------------------------------
* Object: Generic Controler to handle Policy,Small Business Logic, Glue in between components, ...
* Status: Release Candidate
* Author: Fulup Ar Foll fulup@iot.bzh
* Date : August-2017
## Functionalities:
- Create an application dedicate controller from a JSON config file
- Each controls (eg: navigation, multimedia, ...) is a suite of actions. When all actions succeed control is granted, if one fail control acces is denied.
- Actions can either be:
+ Invocation to an other binding API, either internal or external (eg: a policy service, Alsa UCM, ...)
+ C routines from a user provider plugin (eg: policy routine, proprietary code, ...)
+ LUA script function. LUA provides access to every AGL appfw functionalities and can be extended from C user provided plugins.
## Installation
- Controler is a native part of AGL Advance Audio Framework but may be used independently with any other service or application binder.
- Dependencies: the only dependencies are audio-common for JSON-WRAP and Filescan-utils capabilities.
- Controler relies on LUA-5.3, when not needed LUA might be removed at compilation time.
## Config
Configuration is loaded dynamically during startup time. The controller scans CONTROL_CONFIG_PATH for a file corresponding to pattern
"onload-bindername-xxxxx.json". When controller runs within AAAA binder it searches for "onload-audio-xxxx.json". First file found in the path the loaded
any other files corresponding to the same pather are ignored and only generate a warning.
Each bloc in the configuration file are defined with
* label: must be provided is used either for debugging or as input for the action (eg: signal name, control name, ...)
* info: optional used for documentation purpose only
### Config is organised in 4 sections:
* metadata
* onload defines the set of action to be executed at startup time
* control defines the set of controls with corresponding actions
* event define the set of actions to be executed when receiving a given signal
### Metadata
As today matadata is only used for documentation purpose.
* label + version mandatory
* info optional
### OnLoad section
Defines startup time configuration. Onload may provide multiple initialisation profiles, each with a different label.
* label is mandatory. Label is used to select onload profile at initialisation through DispatchOneOnLoad("onload-label") API;
* info is optional
* plugin provides optional unique plugin name. Plugin should follow "onload-bindername-xxxxx.ctlso" patern
and are search into CONTROL_PLUGIN_PATH. When defined controller will execute user provided function context=CTLP_ONLOAD(label,version,info).
The context returned by this routine is provided back to any C routines call later by the controller.
* lua2c list of LUA commands shipped with provided plugin.
* require list of binding that should be initialised before the controller starts. Note that some listed requirer binding might be absent,
nevertheless any present binding from this list will be started before controller binding, missing ones generate a warning.
* action the list of action to execute during loadtime. Any failure in action will prevent controller binding from starting.
### Control section
Defines a list of controls that are accessible through (api="control", verb="request", control="control-label").
* label mandatory
* info optional
* privileges needed privileges to request this control
* action the list of actions
### Event section
Defines a list of actions to be executed on event reception. Even can do anything a controller can (change state,
send back signal, ...) eg: if a controller subscribes to vehicule speed, then speed-event may ajust master-volume to speed.
* label mandatory
* info optional
* action the list of actions
### Actions Categories
Controler support tree categories of actions. Each action return a status status where 0=success and 1=failure.
* AppFw API, Provides a generic model to request other bindings. Requested binding can be local (eg: ALSA/UCM) or
external (eg: vehicle signalling).
* api provides requested binding API name
* verb provides verb to requested binding
* args optionally provides a jsonc object for targeted binding API. Note that 'args' are statically defined
in JSON configuration file. Controler client may also provided its own arguments from the query list. Targeted
binding receives both arguments defined in the config file and the argument provided by controller client.
* C-API, when defined in the onload section, the plugin may provided C native API with CTLP-CAPI(apiname, label, args, query, context).
Plugin may also create LUA command with CTLP-LUA2C(LuaFuncName, label, args, query, context). Where args+query are JSONC object
and context the value return from CTLP_ONLOAD function. Any missing value is set to NULL.
* LUA-API, when compiled with LUA option, the controller support action defined directly in LUA script. During "onload" phase the
controller search in CONTROL_LUA_PATH file with pattern "onload-bindername-xxxx.lua". Any file corresponding to this pattern
is automatically loaded. Any function defined in those LUA script can be called through a controller action. LUA functions receive
three parameters (label, args, query).
## Config Sample
Here after a simple configuration sample.
```
{
"$schema": "ToBeDone",
"metadata": {
"label": "sample-audio-control",
"info": "Provide Default Audio Policy for Multimedia, Navigation and Emergency",
"version": "1.0"
},
"onload": [{
"label": "onload-default",
"info": "onload initialisation config",
"plugin": "ctl-audio-plugin-sample.ctlso",
"require": ["intel-hda", "jabra-usb", "scarlett-usb"],
"actions": [
{
"label": "onload-sample-cb",
"info": "Call control sharelib install entrypoint",
"callback": "SamplePolicyInit",
"args": {
"arg1": "first_arg",
"nextarg": "second arg value"
}
}, {
"label": "onload-sample-api",
"info": "Assert AlsaCore Presence",
"api": "alsacore",
"verb": "ping",
"args": "test"
}, {
"label": "onload-hal-lua",
"info": "Load avaliable HALs",
"lua": "Audio_Init_Hal"
}
]
}],
"controls":
[
{
"label": "multimedia",
"actions": {
"label": "multimedia-control-lua",
"info": "Call Lua Script function Test_Lua_Engin",
"lua": "Audio_Set_Multimedia"
}
}, {
"label": "navigation",
"actions": {
"label": "navigation-control-lua",
"info": "Call Lua Script to set Navigation",
"lua": "Audio_Set_Navigation"
}
}, {
"label": "emergency",
"actions": {
"label": "emergency-control-ucm",
"lua": "Audio_Set_Emergency"
}
}, {
"label": "multi-step-sample",
"info" : "all actions must succeed for control to be accepted",
"actions": [{
"label": "multimedia-control-cb",
"info": "Call Sharelib Sample Callback",
"callback": "sampleControlNavigation",
"args": {
"arg1": "snoopy",
"arg2": "toto"
}
}, {
"label": "navigation-control-ucm",
"api": "alsacore",
"verb": "ping",
"args": {
"test": "navigation"
}
}, {
"label": "navigation-control-lua",
"info": "Call Lua Script to set Navigation",
"lua": "Audio_Set_Navigation"
}]
}
],
"events":
[
{
"label": "Vehicle-Speed",
"info": "Action when Vehicule speed change",
"actions": [
{
"label": "speed-action-1",
"callback": "Blink-when-over-130",
"args": {
"speed": 130
"blink-speed": 1000
}
}, {
"label": "Adjust-Volume",
"lua": "Adjust_Volume_To_Speed",
}
]
},
{
"label": "Reverse-Engage",
"info": "When Reverse Gear is Engage",
"actions": [
{
"label": "Display-Rear-Camera",
"callback": "Display-Rear-Camera",
}, {
"label": "Prevent-Phone-Call",
"api" : "phone",
"verb" : "status",
"args": {
"call-accepted": false
}
}
]
},
{
"label": "Neutral-Engage",
"info": "When Reverse Neutral is Engage",
"actions": [
{
"label": "Authorize-Video",
"api" : "video",
"verb" : "status",
"args": {
"tv-accepted": true
}
}
]
}
]
}
```
|
