diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2021-10-14 16:48:28 +0200 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2021-10-20 22:14:04 +0200 |
| commit | f27d7f9362a0291ff64e97f70ae70a11b74a906c (patch) | |
| tree | 1b448ef795e0b181144ee7adb67896c66bf0dfc1 /cli/mmcli-modem-signal.c | |
| parent | 92539fa71f015e5af08794e486b1c9853c9cf510 (diff) | |
iface-modem-signal: bind together polling and threshold based setups
The values exposed in the Signal interface must not be cleared every
time polling is disabled, because the user may have also enabled
threshold based loading. And viceversa; if the user disables threshold
based polling, we should not unconditionally clear the values as
polling may still be enabled.
We setup a common Private context associated to the interface, and we
keep the current state there, which is also in sync with the DBus
interface.
We will only clear the signal values if both polling-based and
threshold-based setups are disabled.
Following the same reasoning, the mm_iface_modem_signal_update()
method used by implementations to report new signal quality details
is updated so that it's a no-op if no polling-based or threshold-based
setup has been enabled.
Diffstat (limited to 'cli/mmcli-modem-signal.c')
0 files changed, 0 insertions, 0 deletions