c910520f4d
To make the scanner module more understandable and more streamlined, I reworked the update mechanism of the scanner. The scanner tracks now the parameters that were used to enable it and the reason why it is running. This facilitates state logic and allows other modules to "start the scanner", altough it is already running. This is mostly a refactoring and not a functional change. Added a test to verify the behavior. Signed-off-by: Jan Müller <jan.mueller@nordicsemi.no> add to task |
||
|---|---|---|
| .. | ||
| crypto | ||
| data/bt_data_parse | ||
| ecc | ||
| host_mocks | ||
| id | ||
| keys | ||
| CMakeLists.txt | ||