Will modem inhibition truly release MBIM port ?

Edward Chang edward.chang.foxconn at gmail.com
Thu Sep 10 12:14:04 UTC 2020

Hi Aleksander,
                       We are now implementing qualcomm device update (qdu)
MBIM device service on the libmbim currently used by the MM and fwupd.
                       It uses the MBIM_SERVICE_INTEL_FIRMWARE_UPDATE
                       We found the update process will succeed only if the
modemmanager is stopped and the mbim port is opened without the proxy.
                       Probably the mbim interface could not be
interfered during the update process.
                       Could we stop the mbim-proxy during update and
restart it after update ?

Edward Chang

On Thu, Sep 10, 2020 at 5:37 PM Aleksander Morgado <aleksander at aleksander.es>

> Hey Edward
> >  I am implementing a new firmware update mechanism with fwupd and
> libmbim for new 5G modules. This new update mechanism has to use mbim port
> directly (The mbim port cannot be opened with the proxy flag and cannot be
> accessed by others during update.). I found that even if a modem is
> inhibited, its mbim port still couldn't be accessed without the proxy flag.
> I checked the log of modemmanager during inhibition. I saw the mbim port
> closed(but with some transaction time out) and the modem disabled. When the
> mbim modem was inhibited, I expected its mbim port could be accessed by
> others without the proxy flag but it was still required. Would you have any
> advice on this ? Is it possible to release mbim port when a mbim modem is
> inhibited ?
> The device inhibition applies to ModemManager only, and the mbim-proxy
> process has its own lifetime once it has been spawned. The mbim-proxy
> is required to be running because the MM plugin in fwupd needs it for
> QMI PDC operations using QMI over MBIM.
> Why do you need to access the MBIM port directly without the proxy?
> Every operation that you could do without the proxy should be doable
> with the proxy as well. Which MBIM command do you need to trigger the
> firmware update?
> The only reason I can think of is that you're going to use a different
> MBIM library/program to talk to the modem from fwupd, is that the
> case? If so, why not add the necessary new messages to libmbim and use
> libmbim from within the new fwupd plugin support? the MM plugin in
> fwupd already requires libqmi, it could also require libmbim as well
> for what it's worth.
> --
> Aleksander
> https://aleksander.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200910/3057487e/attachment.htm>

More information about the ModemManager-devel mailing list