diff options
| author | Florian Eckert <fe@dev.tdt.de> | 2024-03-18 13:56:23 +0100 |
|---|---|---|
| committer | Dan Williams <dan@bigw.org> | 2024-04-07 01:43:34 +0000 |
| commit | 07526df59b7d9b9054f0431dce7ec7ac8f1e53d4 (patch) | |
| tree | fa73641233a881cce5e6e03d3eef838a78d0d103 | |
| parent | b1aaa4c6b9f76d2cf856c245b76845a8bc215475 (diff) | |
mm-broadband-modem-qmi: always trigger an operator description update
Currently, the operator description update is only triggered once in the
entire update process. But this can lead to a operator description
updated at the wrong time. And is therefore possibly wrong.
The deprecated API call 'qmi_client_nas_get_serving_system' always triggers
an update of the operator description in there subfunction of the callback.
This is missing for the API call 'qmi_client_nas_get_system_info'. To solve
this, an update is now also triggered in the subfunction callback if there
is new system info available.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
| -rw-r--r-- | src/mm-broadband-modem-qmi.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/mm-broadband-modem-qmi.c b/src/mm-broadband-modem-qmi.c index dd0d624c..6c0add38 100644 --- a/src/mm-broadband-modem-qmi.c +++ b/src/mm-broadband-modem-qmi.c @@ -3969,6 +3969,9 @@ common_process_system_info_3gpp (MMBroadbandModemQmi *self, /* Update act and location info */ mm_iface_modem_3gpp_update_access_technologies (MM_IFACE_MODEM_3GPP (self), act); mm_iface_modem_3gpp_update_location (MM_IFACE_MODEM_3GPP (self), lac, tac, cid); + + /* Update operator name and operator description */ + mm_iface_modem_3gpp_reload_current_registration_info (MM_IFACE_MODEM_3GPP (self), NULL, NULL); } static gboolean |