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
|
# 4a-hal-generic for 4A (AGL Advance Audio Architecture).
------------------------------------------------------------
* Object: Use a new api to centralize call to hals, automatically create hal api from configuration files
* Status: In Progress (master)
* Author: Jonathan Aillet jonathan.aillet@iot.bzh
* Date : June-2018
## Cloning repositories for current version
### Cloning 4a-hal-generic with its submodules
git clone --recurse-submodules https://github.com/iotbzh/4a-hal-generic.git
### Cloning 4a-softmixer hal-rc1 version (needed to make work '4a-hal-generic') with its submodules
git clone --recurse-submodules -b hal-rc1-sandbox https://github.com/iotbzh/4a-softmixer.git
### Cloning 4a-alsacore with its submodules
git clone --recurse-submodules https://gerrit.automotivelinux.org/gerrit/src/4a-alsa-core
## Quick introduction to how hal are handled with 4a-hal-generic
* At startup of the 4a-hal binding, a new api called '4a-hal-manger' will be created.
This api is meant to provide verbs to list the loaded hals in your system and to know there current status.
* The '4a-hal-manager' will also create a new hal for each audio configuration files found.
These configuration files are used by the controller and are meant to be used with a mixer.
* External hal (e.g. loaded in another binding) can be loaded/unloaded into '4a-hal-manger' by reaching it
with this hal. It must provide information such as 'api' and 'uid' at loading. It must also provide
a subscription to an event that the '4a-hal-manager' will use to know this hal status.
WARNING: not fully implemented yet.
## Preparation
### Install Alsa Loopback
You must have snd-aloop enabled as a module in the running kernel.
Check that this way on the target:
```bash
zcat /proc/config.gz | grep CONFIG_SND_ALOOP
CONFIG_SND_ALOOP=m
```
If it is not the case, run menuconfig and enable it under:
> Device Drivers > Sound card support > Advanced Linux Sound Architecture > Generic sound device
```bash
sudo modprobe snd-aloop
```
### Create a new hal json configuration corresponding to your audio hardware configuration
#### Information about audio json configuration files
* All audio hardware configuration files are a json description of your audio devices.
* They all must be in ./4a-hal-cfg-reference or ./4a-hal-cfg-community and must begin with 'hal-4a'.
* You can found some examples of these configurations in this directory.
* Each configuration file found at startup will create a new hal with its own api.
* At 'init-mixer' hal command, your mixer configuration will be sent.
#### What you need to set in this configuration file to make your audio work
* In `metadata` section:
* The `uid` field must be the path to your alsa audio device.
* The `api` field should be changed to the desired application framework api of your hal
* For `onload`, `controls`, and `events` sections, please look at the controller documentation
(In ./app-controller/README.md)
* In `halcontrol` section:
* WARNING: use of this section is not yet implemented
* This section is where you put controls which are alsa control calls
* If a control is not available, it will be registered in alsa using '4a-alsa-core'
* These controls will be available as verb for your hal api using 'card/' prefix
* In `halmixer` section (what it is passed to the mixer):
* The `uid` field will be the name of the mixer corresponding to your hal
* The `mixerapi` field should contain the name of the api to call for reaching the mixer
(not need to be changed if you use '4a-softmixer').
* The `backend` section will contain your audio information (such as the path to you alsa audio device
and the configuration of your device).
* In `frontend` section:
* In `ramps` section: will be defined the ramp that you can use in your mixer (ramps in example files can be used).
* In `zones` section: (zones in example files can be used)
* You can define the zones that you want for your mixer.
* You must define which sink will be used in these zones.
* These zones will be used to define streams.
* In `streams` section: (streams in example files can be used)
* You can define the streams that you want for your mixer.
* It must contain:
* A `uid` field (which will be used to reach the stream).
* The `zone` field must correspond to the wanted zone of the stream.
* The `ramp` field must correspond to the wanted ramp of the stream.
* Other fields are optionals
## Compile (for each repositories)
```bash
mkdir build
cd build
cmake ..
make
```
## Using '4a-hal' binder
### Run your binder from shell
```bash
afb-daemon --name=afb-4a --workdir=$PATH_TO_4a-softmixer/build --binding=$PATH_TO_4a-alsa-core/build/alsa-binding/afb-alsa-4a.so --binding=$$PATH_TO_4a-softmixer/build/package/lib/softmixer-binding.so --binding=$PATH_TO_4a-hal-generic/build/4a-hal/4a-hal.so --roothttp=$PATH_TO_4a-softmixer/build/package/htdocs --no-ldpaths --port=1234 --token= -vvv
```
### Connect your binder
Connect to your 4a binder using afb-client-demo
```bash
afb-client-demo ws://localhost:1234/api?token=
```
### List the loaded hal
In the connected client, try to list the loaded hal:
```4a-hal-manager loaded```
And now with more information:
```4a-hal-manager loaded { "verbose" : 1 }```
### Play with an 'internal' hal (described in a json configuration file)
#### Get streams information
Now, you can obtain streams information of your initialized internal hal:
```4a-hal-*halapiname* list```
All the streams listed are available as a verb of the hal api using `name` field.
You can also get the corresponding card id of the stream in `cardId` field.
The card id stream format is `hw:X,X,X` and can be used to play music.
#### Play some music into a stream
WARNING: Current version does not handle audio rate conversion, using gstreamer
or equivalent with audio hardware params is mandatory.
Use the previously obtain card id to play audio in the selected stream:
`gst123 --audio-output alsa=hw:X,X,X your_audio_file.mp3`
#### During playing, try the stream commands to change/ramp volume
Now you can use your hal api to send commands to mixer. This way, you can change/ramp volume :
`4a-hal-*halapiname* *selected_stream* { "volume" : "+10" }`
`4a-hal-*halapiname* *selected_stream* { "volume" : 70 }`
`4a-hal-*halapiname* *selected_stream* { "ramp" : "-10" }`
`4a-hal-*halapiname* *selected_stream* { "ramp" : 100 }`
#### Warning
Alsa try to automatically store current state into `/var/lib/alsa/asound.state`
that may result to odd situation during development/testing. In order to clean
up your Alsa snd-aloop config, a simple `rmmod` might not be enough in some case
you may have to delete `/var/lib/alsa/asound.state` before applying `modprobe`.
In case of doubt, check with following command that you start from a clear green field
```bash
rmmod snd-aloop && modprobe --first-time snd-aloop && amixer -D hw:Loopback controls | grep vol
```
### Load an 'external' hal
To load an external to '4a-hal-manger', you need to you use an 'api_call' from you hal binding.
With this 'api_call' you must sent a json description of your api:
```json
{
"api" : mandatory, string that is your hal binding api
"uid" : mandatory, string that specify your hal uid (usually the device used by your hal)
"info" : optional, string that describes your hal
"author" : optional, string that says who is the author of your hal
"version" : optional, string that says what is the version of your hal
"date" : optional, string that says the date of your hal
}
```
Your hal must also have a 'subscribe' verb available and event name 'hal_status'.
At external hal loading, the '4a-hal-manager' will subscribe to this event.
Within your hal, you must generate an event each time the status of your hal changes.
## What is missing in this version
* Check that external hal really exist at loading
* Handling external hal status events.
* Generation of an '4a-hal-manager' event when a hal status change.
* At mixer initialization, check that the specified device is not already used by another hal.
* Dynamic handling of USB devices.
* Update to the latest version of the softmixer.
|
