diff options
| author |   Aleksander Morgado <aleksander@aleksander.es> | 2021-01-21 11:28:24 +0100 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2021-01-22 10:08:30 +0000 |
| commit | 0e19a0e0536cfc33c23db9bd9f913c835e856dee (patch) | |
| tree | 98ecbc242fe8eb186f06984524010550d93472b9 /docs | |
| parent | b6856d65905a3c81b9457d7dd9bd741d26fc81f8 (diff) | |
libqmi-glib,device: make the net link APIs not depend on QRTR
There's no real relationship between QRTR and these link management
APIs, e.g. we could also use the rmnet based link management on the
SoCs using RPMSG control ports with the bam-dmux kernel driver.
Just make these new APIs be unconditionally available, and if the
kernel driver doesn't support the operations, an error will be
returned to the user.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/reference/libqmi-glib/libqmi-glib-common.sections | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/reference/libqmi-glib/libqmi-glib-common.sections b/docs/reference/libqmi-glib/libqmi-glib-common.sections index f402864..6ee1e25 100644 --- a/docs/reference/libqmi-glib/libqmi-glib-common.sections +++ b/docs/reference/libqmi-glib/libqmi-glib-common.sections @@ -88,6 +88,10 @@ qmi_device_get_service_version_info_finish qmi_device_open_flags_build_string_from_mask qmi_device_release_client_flags_build_string_from_mask qmi_device_expected_data_format_get_string +qmi_device_add_link +qmi_device_add_link_finish +qmi_device_del_link +qmi_device_del_link_finish <SUBSECTION QrtrSupport> QMI_DEVICE_NODE QMI_DEVICE_MUX_ID_AUTOMATIC @@ -96,10 +100,6 @@ qmi_device_new_from_node qmi_device_new_from_node_finish qmi_device_get_node qmi_device_peek_node -qmi_device_add_link -qmi_device_add_link_finish -qmi_device_del_link -qmi_device_del_link_finish <SUBSECTION Standard> QmiDeviceClass QMI_DEVICE |